Hi
Sounds like somebody has changed the security on the workgroup, find a file called wrkgadm, and see what secruity file has been used. Security files end in .MDW. Trying changing it to system.mdw, which should be on your PC somewhere.
Also how did you enter a password, did you set the...
Not tried this, but you'll find that most anti-virus software already has checks for the virus in them, so as long as PCs have anti-virus software, it shouldn't be anything to worry about
also worth making sure that all access versions are the same, including your ADO and RDO versions, if you have incompatation ADO and RDO these can slow down the reterival time.
Have u considering storing data in SQL Server with Access front end??
I wonder if this is because access is only exporting the values of the underlying table, not sure if Access is capable for exporting calculations based on reports. Try doing some calcs in your query to see if it exports these.
Are you attempting to compact/repair from the same PC each time, if so try a different computer. Also try defragging hard drive in case data is being stored in correctly on your computer.
Also are you running any VBA code in the background which might alter data in any way in your underlying...
The overflow error occour when access is trying to perform a calcuation outside of the variable range. Look through each of your queries and search for the word #error, in any of the fields, you will probably find that their is a calculaton being performed that access doesn't like. /0 for example.
Have u tried disconnecting the PC from the Network and running the process just in case. Also worth making sure that their are no linked tables in the database, in case something has sneaked in, which might still be connecting to a file on the network somewhere.
I encountered the same problem using my Novell Network a few years ago. Are u running Access Version 2 by any chance? If the database has it's records stored on the network and the front end stored on the machine, the lock error could still occour.
The quick solution is to move the records...
Unfortunately their is no easy way to migrate Lotus Approach to Access, you can move the tables over into access, but you will have to redesign all of the forms and reports and relationships yourself.
If their is such a tool out their, the chances are it will cost you quite a bit.
This may not be a corrupt database, your program appears to be using a OBDC link to your access database, see if you can open the database in Microsoft Access and compact/repair their.
Check to see if their is a workgroup file that belongs with this database. If their is one, you will need to join the workgroup, type in a password, and then hopefully it will allow you to view/convert the database correctly.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.