Advice from fellow techies!

Afternoon,

if this is a simple fix, I apologise but after the meetings from hell this morning my head has turned into mush!

Got a user hooking up to an SQL database there is a training version and a test version, user can hook up to the live version without a problem, try to hook up to the test version and you get the following error:

Crystal Reports: Database Error

ODBC error: [Cache][ODBC] SQLDriverConnect - State S1000
[C:\Program Files\Seagate Software\SI\X86\cqw32.exe]
Cache SQL ODBC Driver Error 25031

I checked the system DSN's and there all correct.

I assumed at first it was a GPO error with the user not having access to that program file group, I checked the policy and low and behold the users have access to the program folder with full rights?

Am I missing something under my nose? My head is just full of mush today!

Cheers

Rich

[Stingo]

Blimey mate - you've got 'em all stumped!!

try deleting the cached queries and trying again?

are you running custom collation sequence on the server?

Googled the error code and it came up with "primary key error"
But I'll guess that you'd done that anyway.

Originally Posted by Gnan

try deleting the cached queries and trying again?

are you running custom collation sequence on the server?

Done that already, same error.


Cheers though

Rich

P.S. I did google but no joy!

[TSM]

Originally Posted by tricky

Googled the error code and it came up with "primary key error"
But I'll guess that you'd done that anyway.

Same here.

http://www.faircom.com/support/ctree...e=sqlrefb3.htm

Just do a find for 25031

Faircom? c-tree? They still in business then? Heck, that takes me back to my 'c' programming days. No SQL in c-tree in those days; eee, bah gum.

How are you connecting to the database, direct or via a third party like Citrix, have that sort of error because the citrix sign on is pointing at the wrong database for the start up script.
H

Originally Posted by the_runt69

How are you connecting to the database, direct or via a third party like Citrix, have that sort of error because the citrix sign on is pointing at the wrong database for the start up script.
H

Hooking up directly, with the system DSN's added and with specifying the database when they start up the program, they are using the correct username and password, it works fine on some of the PC's. I went over them with a fine toothcombe and could not find any differences in the settings!

Its bugging me, might have another look at it this afternoon with a fresher head.

Ruddy Ad Hoc report writer, its nothing but grief.

Cheers

Rich