Access 97/Jet 3.5: Problem with data refresh in a multi-user database

[RipTide]

Background:
Using an unsupported/abandoned multi-user multi-database program that uses
Access 97 and Jet 3.5. Program itself appears to have been built with
PowerBuilder 6.5.
Databases reside on an NT 4 SP6 file server with opportunistic locking disabled.
Workstations are Win98 SE with Access 97, Jet 3.5 SP3, and Network
redirector file caching disabled (VREDIR/DiscardCacheOnOpen=1)
Network: Local LAN using NETBUEI as Primary Protocol, than TCP/IP.

Problem:
When multiple users open the same database, and access the same record,
and the data for that record is modified everyone can see it on the screen,
but it will not print out the modified data until the first person that opened
the record closes his connection to the database.
However, if the first person to access a record makes the modification,
his print out will be correct, but subsequent users will still print the unmodified
data until the initial user closes his connection to the database.

Problem with data refresh, workstation file caching, ODBC/Jet caching ?
I have not been able to figure out if the problem lies within Jet 3.5 and it's
handling of multi-user databases over a network, or with the programming
of the database.

Your expert insight is much appreciated.

Thanks.

Arneil
ri*****@cryogen.com

[Albert D. Kallal]

What you describe is not the behaviour of ms-access.

However, since you state that the developer did not use ms-access, but in
fact wrote the application in PowerBuilder, then I would suggest you talk to
the developer.

It is very possible that the original developer used temp tables, or perhaps
even wrapped the updates in a trans action of some type.

If one was using ms-access, then the code to force a disk write would be a
me.refresh right before the report gets printed (assuming that the user is
still editing the one record, and whacks a button to print that record based
on a report).

Since the ordinal author could have coded the application anyway they
want...then I would suggest you check with the original developer.

I *did* think that PowerBuilder was a Sybase tool that is for use with the
Sybase database server, and not one that can be used with JET. Perhaps you
meant Delphi..but regardless, how the updates to data works is really the
choice of the developer.

There should be no need to close the application for others to see the
updates. That being the case, then how the application is coded is at issue.
--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
No************@msn.com
http://www.attcanada.net/~kallal.msn

[Arneil jaski]

Thanks for the reply. As far as the application

being created or related to PowerBuilder may

or may not be true as I read some readme.txt

in the install directory. The datbase is an

MDB file, and will not work unless Access 97 and

Jet 3.5 is installed (won't function at all with

Jet 4.0+)

They only have problems when accessing the same

database and the same record. I was hoping there

was something I could do as far as a setting

somewhere to fix the record refresh.

The developer does not exist anymore so if it

has to go that far we might as well develop

another one, maybe with MySQL or something.

Thanks again.

Arneil

ri*****@cryogen.com

"Albert D. Kallal" <pl********************@msn.com> wrote in message
news:s49tb.390570$9l5.28842@pd7tw2no...

What you describe is not the behaviour of ms-access.

However, since you state that the developer did not use ms-access, but in
fact wrote the application in PowerBuilder, then I would suggest you talk to the developer.

It is very possible that the original developer used temp tables, or perhaps even wrapped the updates in a trans action of some type.

If one was using ms-access, then the code to force a disk write would be a
me.refresh right before the report gets printed (assuming that the user is
still editing the one record, and whacks a button to print that record based on a report).

Since the ordinal author could have coded the application anyway they
want...then I would suggest you check with the original developer.

I *did* think that PowerBuilder was a Sybase tool that is for use with the
Sybase database server, and not one that can be used with JET. Perhaps you
meant Delphi..but regardless, how the updates to data works is really the
choice of the developer.

There should be no need to close the application for others to see the
updates. That being the case, then how the application is coded is at issue.

--
Albert D. Kallal (MVP)
Edmonton, Alberta Canada
No************@msn.com
http://www.attcanada.net/~kallal.msn