Urgent help requested.
I have a VB6 app using DAO/Jet to access an MDB on a Novell server from two different NT 4.0 Work Stations.
The App does a loop through all database objects for the Jet workspace when it ends to make all database references are closed.
The problem:
Work station 1 is reviewing and making changes to data.
Work station 2 is reviewing the same data but does not see the changes, event after loading the form, or starting the application again, even 30 minutes later.
If WS 1 restarts the app, he sees the changes he made.
When the MDB is copied locally onto WS 2 and is opened with MS Access, he sees the changes in the table. If he starts the application again, he still sees the old data.
The User of WS 2 claimsto not see the new data even after a reboot of the WS.
One thing We noticed is that the change date of the MDB file on the server is still from yesterday. Normally when all users who opened an MDB, close out, the MDB file date is changed, and theLDB lock file is erased.
I have no experience with Novell, and very little with servers at all. I am trying to find out myself but time is running out here to get this to work.
Any help would be highly appreciated!