Programming on SQL Server 7 with VB(using ADO)

[Addisu Mulat]

I have just started programming on SQL Server 7 with VB(using ADO). What
I have encountered is strange for me, its like this, I have programmed the
database (for multiuser environment) by making the lock type of the recordset
adLockPessimistic, I wanted the user to view changes if he wanted to by explicitly
refreshing the data himself but what happened is the changes made by user
user1 on one terminal is viewed by another user user2 on another terminal
without user2 explicitly refreshing the data. This happens for tables with
primary key but not for the other ones. How does this happen and how do I
solve the problem?

I look forward to your response.

thank you,
Addisu

[Rob Vieira]

Realistically, any table should have a primary key!

That said, I'm still a little confused by the scenario you're providing. Can
you expand on it a bit?


--
Rob Vieira MCSD, MCT, MCDBA
www.ProfessionalSQL.com

"Addisu Mulat" <addisumulat@hotmail.com> wrote in message
news:3a6e7ea4$1@news.devx.com...
>
> I have just started programming on SQL Server 7 with VB(using ADO).
What
> I have encountered is strange for me, its like this, I have programmed the
> database (for multiuser environment) by making the lock type of the
recordset
> adLockPessimistic, I wanted the user to view changes if he wanted to by
explicitly
> refreshing the data himself but what happened is the changes made by user
> user1 on one terminal is viewed by another user user2 on another terminal
> without user2 explicitly refreshing the data. This happens for tables with
> primary key but not for the other ones. How does this happen and how do I
> solve the problem?
>
> I look forward to your response.
>
> thank you,
> Addisu
>
>