- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
You say corrupt, in what way exactly? Do you get any specific error numbers/messages?
Have you tried Access repair program? Compact and Repair. If not, use it. But ensure that you made a backup, it is necessary because all the recovery tips can make the damage even worse.
Also try Jet Compact Utility. This tool created by Microsoft and it is much like Compact and Repair, but more successful in repairing.
If no one of above advice helps, then perhaps you need more powerful solution. In this case try to run a good third-party. I would recommend Recovery Toolbox for Access. It must help you. https://access.recoverytoolbox.com/
back up files on external hard drive!! mirror hard drive, will keep corrupted file, it might cause further problems. you have lost some critical files, but you might have isolated a virus . Move on, do a clean install, after reload the backed up files one at a time.
error 3343 is a database error. Unfortunately, PCCharge is still in the stone-ages of computer technology and they think VB6.0 and MS Access 2.0 are stable and secure ... At any rate. 3343 is simply an unrecognizable database, in this case due to corruption. There is a program in the PCCharge directory called VisData. This will allow you to run a repair and compact the database. To use: First make a backup of your PCCW.MDB database in your PCCharge directory (C:\Program Files\Active-Charge (PaymentServer); C:\Program Files\PCCW (PRO)).
Execute VISDATA.exe. File -> Repair MDB. Select the PCCW.MDB database from your PCCharge directory. Select 'No" to open Repaired Database. File -> Compact MDB ... 2.0 MDB Again, Select the PCCW.MDB It will then prompt for what you want the database to be named. Simply select PCCW.MDB again, select 'YES' to replace existing database. Select 'NO' to encrypt database. Select 'NO' to Open Compacted database Exit Visdata and start PCCharge.
It would also be a good idea to go ahead and update to the latest available Scripting Runtime library. This can be found by going to microsoft.com and searching for the phrase 'windows script'. (To my knowledge, 5.7 is the latest version).
You probably have a earlier pervasive version installed or no version. You will get this error when either of those occur. Pervasive workstation is all you need. There should be an option to install it from the peachtree cd. If not open the cd and browse for a pervasive directory and run the setup.
If they didn't include it then you can download it from Pervasive. You should get V10 workgroups install and that error should go away.
This error occurs when the user doesn't have XML Core Services 4.0 SP2
intstalled on the local workstation. To download the service pack
either go to Microsoft's website or go to google.com search engine and
enter "Download XML Core Services 4.0 SP2." To intall the service pack,
have an administrator login and run the downloaded file.
I had the same problem but it was with Simply 2007 running on a Windows XP computer. One day it just said "username and password are incorrect" even though I had just used it the day before with the exact same username and password (I am the administrator). I Googled all kinds of solutions to try, and finally this one worked. I simply did a Windows "System Restore" to the previous day. Once I did that, Simply Accounting allowed me to log in again. Therefore it tells me that the problem is one of two things...either the Windows database engine...or with some sort of Windows Update or other program update that interfered with the login process. The likelyhood is that it's a Windows system file involved in the database engine that was corrupt.
If you don't have automatic System Restore setup on your Windows computer however, then you are out of luck. The only possible solution (I haven't tried it) is to copy all the Simply database files to another working computer that "hopefully" doesn't have the same corrupt system files, and try to install and run the program and database from that computer, it may work.
try checking to see if the company exists in the database setup.
you need to make sure the company database is linked to the system database before it becomes available to use. if it is there, delete the links and recreate them