By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
458,193 Members | 1,812 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 458,193 IT Pros & Developers. It's quick & easy.

Too few parameters expected 2 error occurs after migrating "MS Access 2000" to "MS SQL Server"

P: n/a
Hello all

I get Too few parameters expected 2 error and "The MS Jet Database
engine cannot find the input table or query "myTempTablename". Make
sure it exists and that its name is spelled correctly. 3078" after I
migrated "MS Access 2000" to "MS SQL Server 2000" and relinked all
linked tables.

The front-end interface of my application is MS Access 2000. The
back-end is MS SQL Server 2000. After I migrated the database and
relinked all linked tables, "Too few parameters expected 2" and "input
table or query "myTempTablename" 3078" error occurs. I found a article
in Microsoft website. The "Too few parameter" error occurs because the
limitation of the MS Access ODBC driver. If it is, any solution?

Thanks in advance


Nov 13 '05 #1
Share this Question
Share on Google+
1 Reply

P: n/a
Hi Bon,

If you mean you are getting the error when you are trying to relink the
tables through ODBC, then the problem could be - if your table(s) had a
memo field, that sql server picked up the memo field as a varchar, and
Access is trying to read a text field that exceeds 255 chars. You need
to go to Query Analyzer (sql server QA) and run some queries against the
offending table to see what the text length is in your varchar fields in
the sql server table. And if Sql Server did pick up an Access memo
field as a Sql Server Text field, ODBC can't read Sql Server Text
fields. If any of the varchar fields exceeds 250 chars (for me I get
errors after exceeding 250 chars), then Access ODBC will complain. If
your fields do exceed that and you need to retain the data, then the
trick is to have 2 tables. One is raw/original data, and the other is
truncated data for use with ODBC. You can use ADO to access the
original table (much better than ODBC).



*** Sent via Developersdex ***
Nov 13 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.