Problem w/dbOpenTable, dbDenyRead w/VB5 & Access 97
This problem occurrs because the VB5 running 'automated' to DAO are
not close enough to the LDB locking structure. This problem never
occurs in native MS-Access, only via automation. Now if you could get
all of your VB5 code to automate thru a single instance of Access your
problems would be solved, but then again if that copy of Access goes
south, you are out to lunch.
On Mon, 13 Oct 1997 14:58:35 -0700, "Steve Lukshides"
>I was afraid I'd get an answer like this. This is what we wound up doing
>but I feel it is a messy solution to what appears to be an Access bug. Do
>you have any idea why the dbOpenRead does not work as expected?
>> Hi Steve,
>> For things like that I use a home-built semaphore. Just make a table
>> with a SYMBOL and VAL columns, where SYMBOL is the primary key. Then
>> code a function which updates and clears the VAL column for a given
>> The VAL should identify the workstation or process holding the
>> semaphore in some way.
>> Tacky, I know, but it works.
>> On Thu, 09 Oct 1997 14:28:17 -0700, "Steve Lukshides"
>> >In VB5 I am opening a table type Recordset with dbDenyRead set. This is
>> >supposed to lock the table being opened to prevent other users from
>> >accessing it. For the most part this works, however, if two users
>> >this same line of code at the same time both wind up with access to the
>> >Has anyone experienced this behavior before? Is it solvable?