ERROR!!!! ------ ADODB Recordset Error -2146825023

[Matt]

HELP!!!!!

When using the model against build 729 all works as expected.  We have upgraded one instance to 731 and this error occurs everytime we drag something into a diagram.

No links are created as the object is added, however once saved and refreshed then everything works as would be expected.

This is happening on every single drag action!

EA is running on XP Pro against a SQL Server 2000 model - any and all advice gratefully taken!

Please advise...

Many thanks,

Matt

[Bruno.Cossi]

Hi Matt,

do I understand it properly that you have builds 729 and 731 accessing the same SQL Server Repository? I ma not sure if there is a difference in the DB structures expected between the two builds (I suspect not) or in the way they make some of the DB calls (possible). Either way, does the error happen in both 729 and 731 now?
I would suggest to contact Sparx Systems support directly. In the meantime, try to run this in your SQL Query Analyzer:

SET NOCOUNT ON

and see if it helps.

Bruno

[Matt]

Bruno,

thanks for the response.   To add clarity to the situation:

We built the repository initially using 729, one of the users has upgraded to 731 and has seen the issue as mentioned above, I and the other users are still using 729 and do not see this error at any time.  This means that the error is consistently a 731 error only.

Will try the no count option but not sure if that will help - will update with results on that in a while!

Cheers,

Matt

(Have screen cap, what is the proper way to add to this?)

[Bruno.Cossi]

Matt,

I see. We are using 731 on a repository that has been created using earlier versions, too (once again, I think the db structures do not differ, even though I can't be sure) and have never seen the problem. The problem might be due to the way the 731 user is connecting to the repository, too. You might want to make sure that the connection is setup the same way on his/her computer as on the others.
Screen cap... I do not think you can post it here, if you have a webspace anywhere, you could upload it there and post a link here.

Bruno

P.S. The "NOCOUNT" option will likely not help, it helps with one relatively common occurence of this error, but I doubt it will help here. Generally the best way to find the cause of this error is to run the troublesome SQL statement is SQL Query Analyzer, but that obviously is not possible here.

[TomO]

Hello Matt,

We have found that this error is due to a problem in build 731. It has been resolved in the next build which we are hoping to get out late this week, to early next week (all things going well).

Regards,
Tom O’Reilly
Sparx Systems

[Matt]

Cheers Tom,

any pointers as to what the problem was/is?

Does this occur in all cases, or just special ones?  I was looking at 731 so that I can fully try the bridge but will wait until 732 I guess!

Matt