Global Find 1.0.4, Database Cleanup 1.0.7, and XRefUtility 1.1.3 give same error
Note: This was posted to the TPUSER Yahoo group, but I've not yet received any replies there. My apologies to anyone who might be annoyed by the cross-posting.
When I try to point any of these indispensable utilities at our TestPartner 5.4.0 SQL database, I get the following error message:
"The selected database 'TestPartnerSQLDB' is not a valid TestPartner database."
As installed, the utilities are working fine against the local machine's TestPartner MS-Access database (the default DSN)- and they even work well against the SQL database at the TestPartner installation that resides on the SQL server.
TestPartnerSQLDB is an ODBC System DSN (not a User DSN) defined at the workstations and subsequently configured at TestPartner's Login screen. It works perfectly, so far as TestPartner itself is concerned, to provide connectivity to our SQL 2000 Server SP3a TestPartner database.
I suspect the problem with these utilties is that TestPartner 5.4.0 now supports DSN's that deploy SQL authentication (which we are now
using), instead of Windows NT authentication (which was required by TestPartner 5.3.0 and earlier versions). If this is the problem, how can I configure the utilities to use SQL authentication?
Any ideas? We can live without these precious tools but our quality of life will be significantly reduced. :-)
If my employer's opinions differ from those I express here, let it be understood in advance that they are right and I am wrong.
Re: Global Find 1.0.4, Database Cleanup 1.0.7, and XRefUtility 1.1.3 give same error
The utilities TP Cross Reference, TP Global Find, and TP Database Cleanup have all been updated to support both NT and Database authentication. They are all available for download from either the Yahoo TPUser group or the mrtechguyUtilities group.