Recent content by Hurdles

Thanks for that one - you are quite right, I get Error 91. Yes, the app is working but I cannot open the db in Access. It matters (a) because as something is evidently wrong it may well get worse and (b) because Access is the easiest way to maintain the data. However, I have had to rebuild...

Trying to synch via DAO in VB6 code creates no error. There is a pause, presumably while the databases synchronize, then the test sub exits normally. Trying from Access as you outline behaves the same way. There is no error message when I try to open the replica. I get the hourglass for a...

Using interactive VB6, or the compiled VB6 application I can (a) write and read to the database on Laptop and (b) synch with the replica database on Server. I can then read newly changed data on Server using the compiled application. I cannot open either copy of the database using interactive...

David, Thank you for replying. Q1 - I can no longer open any copy of this database in either Access 2000 or 2003. The evidence is that they are synchronizing properly when addressed by the VB6 application. Q2 - I replicate to the laptop so that I can take, and use, an up-to-date copy of the...

Bob Thank you for commenting. In fact, the replicated databases on each of the three machines are all back-end. The front-end is written in VB6, because it also writes data to Outlook and Excel for certain tasks. This allows quick use of the database on one machine without having to bring up...

I have a small network. Server (Windows SBS 2003 SP"), Workstation and Laptop (both XP SP3). I have Access 2003 on Server and Laptop and Access 2000 on Workstation. I run a replicated database on all three machines, with Laptop holding the design master and Laptop and Workstation both...