Welcome Guest Search | Active Topics | Log In | Register

VistaDB User Forums » VistaDB 3.x » Tools and Data Migration » Errors after migrating from JET
Errors after migrating from JET Options
Previous Topic · Next Topic
isoy
#1 Posted : Friday, June 05, 2009 1:19:17 PM
Rank: Member

Groups: Member

Joined: 6/5/2009
Posts: 14
Points: 42
I'm new here so hello everybody.
I'm migrating from JET and used the data migration wizard.
I was happy to see that the database is much smaller than the JET source (compacted often).
Most tables migrated ok, but some I had to manually change SamllDateTime to DateTime to see the data.

When running the application I get the errors below.
I appreciate any help with it.

Its also not clear to me how to identify the columns by the number.
What does it mean 'ColumnNo=790' ? I don't have 790 columns in my app.

Thanks in advance. smile
Isoy


Error 1:
VistaDB.Diagnostic.VistaDBSQLException was caught
ColumnNo=1
ErrorId=509
LevelMessage="Error 509 (Provider v. 3.5.3.83): Invalid statement: SELECT Line #: 1; Column #: 1"
LineNo=1
Message=" Error 500 (Provider v. 3.5.3.83): Expected symbol: "(" Line #: 1; Column #: 59 Error 509 (Provider v. 3.5.3.83): Invalid statement: SELECT Line #: 1; Column #: 1 "
Source="VistaDB.NET20"
StackTrace: ...



Error 2:
VistaDB.Diagnostic.VistaDBSQLException was caught
ColumnNo=790
ErrorId=616
LevelMessage="Error 616 (Provider v. 3.5.3.83): Parameter not declared: @Param2 Line #: 1; Column #: 790"
LineNo=1
Message=" Error 616 (Provider v. 3.5.3.83): Parameter not declared: @Param2 Line #: 1; Column #: 790 "
Source="VistaDB.NET20"
StackTrace: ...


Error 3:
VistaDB.Diagnostic.VistaDBSQLException was caught
ColumnNo=40
ErrorId=567
LevelMessage="Error 567 (Provider v. 3.5.3.83): Column doesn't exist: ? Line #: 9; Column #: 40"
LineNo=9
Message=" Error 567 (Provider v. 3.5.3.83): Column doesn't exist: ? Line #: 9; Column #: 40 "
Source="VistaDB.NET20"
StackTrace:
Back to top
 Report Abusive | Report SPAM
js_vistadb
#2 Posted : Friday, June 05, 2009 1:38:51 PM
Rank: VistaDB Staff

Groups: Administration, VistaDB Staff

Joined: 8/13/2006
Posts: 3,403
Points: 3,994
Location: Mount Dora, Florida
The column is the column number in the SQL Text.

Looks to me like you have ? based params (SQL Server uses @ to mark paramters). You have to change your SQL script if you are coming from JET - it uses syntax that only works in Access for a lot of things.

Change all parameters to @, not ?.
Put ; at the end of each statement.
Put () around function parameters.
Put [] around reserved keywords.

I am sure there are other Access-isms that you will run into.

Of course the real benefit to taking the time to convert them is that then you SQL code will run on VistaDB and SQL Server.

Jason Short
Back to top
WWW BLOG  Report Abusive | Report SPAM
isoy
#3 Posted : Saturday, June 06, 2009 8:13:49 AM
Rank: Member

Groups: Member

Joined: 6/5/2009
Posts: 14
Points: 42
Hi Jason, thanks a lot for your help in this. It was the access '?' versus '@' issue, as you said. Was fixed, and it now works great!
Thanks again, Yosi
Back to top
 Report Abusive | Report SPAM
Users browsing this topic
Guest
VistaDB User Forums » VistaDB 3.x » Tools and Data Migration » Errors after migrating from JET
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAFPro Theme Created by Jaben Cargman (Tiny Gecko)
Powered by YAF 1.9.3 | YAF © 2003-2009, Yet Another Forum.NET
This page was generated in 0.065 seconds.