Problem w/dbOpenTable, dbDenyRead w/VB5 & Access 97 
Author Message
 Problem w/dbOpenTable, dbDenyRead w/VB5 & Access 97

Hi,

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 execute
this same line of code at the same time both wind up with access to the
table.

Has anyone experienced this behavior before?  Is it solvable?

Steve



Mon, 27 Mar 2000 03:00:00 GMT  
 Problem w/dbOpenTable, dbDenyRead w/VB5 & Access 97

Kurt,

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?

Steve



Quote:
> 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
> SYMBOL,

> The VAL should identify the workstation or process holding the
> semaphore in some way.

> Tacky, I know, but it works.

> Regards,
> Kurt

> On Thu, 09 Oct 1997 14:28:17 -0700, "Steve Lukshides"

> >Hi,

> >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
execute
> >this same line of code at the same time both wind up with access to the
> >table.

> >Has anyone experienced this behavior before?  Is it solvable?

> >Steve



Fri, 31 Mar 2000 03:00:00 GMT  
 Problem w/dbOpenTable, dbDenyRead w/VB5 & Access 97

Sorry Steve,

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.

Kurt

On Mon, 13 Oct 1997 14:58:35 -0700, "Steve Lukshides"

Quote:

>Kurt,

>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?

>Steve



>> 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
>> SYMBOL,

>> The VAL should identify the workstation or process holding the
>> semaphore in some way.

>> Tacky, I know, but it works.

>> Regards,
>> Kurt

>> On Thu, 09 Oct 1997 14:28:17 -0700, "Steve Lukshides"

>> >Hi,

>> >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
>execute
>> >this same line of code at the same time both wind up with access to the
>> >table.

>> >Has anyone experienced this behavior before?  Is it solvable?

>> >Steve



Sat, 01 Apr 2000 03:00:00 GMT  
 
 [ 3 post ] 

 Relevant Pages 

1. VB5 & Excel 97 problem

2. VB5 app. Access 97 intermittant locking problem - help

3. Access 97 problem after VB5 install

4. Problem with VB5 Opening Secured Access 97 DB

5. VB5 and Access 97 slow down problem

6. Access 97 problem after VB5 install

7. Access 97 problem after VB5 install

8. Synchronous database access in Access 97 using VB5

9. Excel 97 VB5 SQL query problem

10. Converting Access 97 forms 2 VB5.0 forms


 
Powered by phpBB® Forum Software © phpBB Group