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 synchronizing with Server. I use Access to help with design, but the application to use this database is written in VB6. It has operated happily for a couple of years.
BUT yesterday I could not open the database on either Server or Laptop, although the VB6 application appears to be working happily. I can open the database on Workstation using Access 2000. I have tried using JETCOMP, but the new databases it creates show the same problem - they do not open and there are no messages; except that, just once, I got: "Cannot open database 'path\filename'. "It may not be a database that your application recognises or the file may be corrupt".
I am loathe to attempt to rebuild the database suite from the surviving Access 2000 copy if there is a better way. Can anyone help?
I run a replicated database on all three machines, with Laptop holding the design master and Laptop and Workstation both synchronizing with Server. I use Access to help with design, but the application to use this database is written in VB6. It has operated happily for a couple of years.
BUT yesterday I could not open the database on either Server or Laptop, although the VB6 application appears to be working happily. I can open the database on Workstation using Access 2000. I have tried using JETCOMP, but the new databases it creates show the same problem - they do not open and there are no messages; except that, just once, I got: "Cannot open database 'path\filename'. "It may not be a database that your application recognises or the file may be corrupt".
I am loathe to attempt to rebuild the database suite from the surviving Access 2000 copy if there is a better way. Can anyone help?
Last edited: