I am no expert, but, you might try uninstalling VB altogether. I have no installation of VB on my test machine and TP works fine.
If you have an installation of Visual Studio on the same machine, that may be an issue. I have found it to be a bad practice to try testing on a development machine. The development environment provides access to additional (and sometimes different) resources than your average user is going to have.
Quality is the result of a carefully constructed cultural environment. It has to be the fabric of the organization, not part of the fabric.
Thanks guys. After I installed 5.2.1 the error message disappeared. But I got another error and it seems I can't find any workaround.
The database pointed to by the DSN 'testpartnerDB'
is at version 26.0.18. This software requires a database at 30.1.20. The database cannot be used until it has been converted. Run the database maintenance program to convert your database to the new schema.
I followed this instruction and the database file has been converted into the new schema but I'm still getting the same error message.
Did anyone encounter this error message before?
Sounds to me like the odbc connector is point to the wrong file. The default connector created by the installation process is "testpartner" not "testpartnerdb". I'd start by looking there, or call CPWR tech support.
You have to use the database maintenance utility provided with TestPartner to convert the old database. There is another quicker method, but use it only if you have no data in your old database. goto
Delete Testpartner.mdb. Make a copy of Template.mdb and rename the copy to Testpartner.mdb