Difference between SQL 2005 and SQL 2005 express

elwin68

Hello,

We have a solution to transfer data between Navision and Microsoft SQL.
Until now we have worked with SQL 2005 and the transfer works very well.
Now we want to transfer data between Navision and SQL 2005 express. We thought the used commands work with both SQL versions.
Unfortunately this is not the case.

The program stuck on the command autRecord.AddNew (autRecord is an automation to 'Microsoft ActiveX Data Objects 2.8 Library'.Recordset).
See the attachment for the error message.

Does anyone know why this works with SQL 2005 and not with SQL 2005 express?

Thanks in advance.

bbrown

Have you configured SQL Express to allow external connections (your linked server)? By default it does not.

elwin68

Hello bbrown,

Thanks for your answer.
Your solution is not the right one because the connection can be made to SQL 2005 Express. Deleting records works fine too, so the link from NAV to SQL 2005 Express is working fine.
When trying to add new records with the command addnew, the error occures.

The code is as follow:

REPEAT
autRecord.AddNew;
Transfer proper fields to record with recordref and fieldref
UNTIL NEXT=0

autRecord.UpdateBatch;

The error occures when autRecord.AddNew is called the second time.

We have changed the code to:
REPEAT
autRecord.AddNew;
Transfer proper fields to record with recordref and fieldref
autRecord.Update;
UNTIL NEXT=0

Now a update-error occures when autRecord.Update is called the first time.

I hope this makes something clear.

stryk

Hi,

well, I'd gladly help you in this case, but unfortunately I'm lacking to speak Dutch.
I guess you'll get more replise to this issue if you could translate this error message into English.

Or switch you NAV client to English and reproduce the error for a new screeneshot ...

But maybe you want to check this site http://www.microsoft.com/sqlserver/2005/en/us/compare-features.aspx to see the differences between the editions ...

elwin68

My fault, of course it must be in english.
The funny thing is that I was translating the error message and beginning to think
I surfed over the internet and found the solution.

Someone had changed the computer name. In the table sys.servers the old computer name still was defined. This must be updated.
All information is found on http://msdn.microsoft.com/en-us/library/ms143799.aspx