G
Graham
I've created an application (front end UI, back end DATA). The Data.mdb is
stored on a server and UI.mdb installed on two clients. Part of the app
includes DiaryReminder functionality. A listbox is populated with just
enough basic info from the recordset for the user to recognise the client
and be prompted to complete a scheduled task. Double-Clicking on the listbox
row opens the main form (filtered to show a single record in the record
selectors), with the Client's full details. The user can then complete the
scheduled task, close the form and move on to the next reminder. This works
perfectly on my home network (win98 Peer to Peer) but has intermittent
problems (Error - Recordset Not Updateable), when installed on the client's
network. NT Server, client1=Windows 2000, cleint2=Windows 98. I don't know
what service packs are installed.
The puzzling thing is, the problem only happens intermittently. It's not a
record locking problem. the situation still occurs on days when the (part
time) user of client2 is not in and the application is only used from
client1.
Client1 does have Access 2000 and Access 97 installed on the same machine.
Anyone have any ideas?
Graham
stored on a server and UI.mdb installed on two clients. Part of the app
includes DiaryReminder functionality. A listbox is populated with just
enough basic info from the recordset for the user to recognise the client
and be prompted to complete a scheduled task. Double-Clicking on the listbox
row opens the main form (filtered to show a single record in the record
selectors), with the Client's full details. The user can then complete the
scheduled task, close the form and move on to the next reminder. This works
perfectly on my home network (win98 Peer to Peer) but has intermittent
problems (Error - Recordset Not Updateable), when installed on the client's
network. NT Server, client1=Windows 2000, cleint2=Windows 98. I don't know
what service packs are installed.
The puzzling thing is, the problem only happens intermittently. It's not a
record locking problem. the situation still occurs on days when the (part
time) user of client2 is not in and the application is only used from
client1.
Client1 does have Access 2000 and Access 97 installed on the same machine.
Anyone have any ideas?
Graham