R
Robin Donald
Whilst trying to link (A2K, Win2K) to a Foxpro table using
the Visual Foxpro driver, we encounter the following
problem.
Although the table seems to open up perfectly, when we run
a query based on the table we get the message:
ODBC--Call failed.
[Microsoft][ODBC Visual FoxPro Driver] Too few arguments.
(#229)
The error message (very helpfully) tells us that error 229
is "too few arguements".
We read the article "Registry Entries (Visual FoxPro ODBC
Driver) which lists the registry details.
When we checked it, our machine had
API Level REG-SZ "0"
but the "0" should have been a "1".
Every other entry line appeared to be perfect.
So we changed it to "1" and re-booted and built a new ODBC
source and relinked and guess what!
Yep. Same old error.
We downloaded the latest Win2K patches and MDAC (2.7) but
all to no avail.
What are we doing wrong.
A colleague at a different site with a similar machine and
settings can run this query perfectly.
PLEASE!!! What are we doing wrong?
Regards
Robin Donald
the Visual Foxpro driver, we encounter the following
problem.
Although the table seems to open up perfectly, when we run
a query based on the table we get the message:
ODBC--Call failed.
[Microsoft][ODBC Visual FoxPro Driver] Too few arguments.
(#229)
The error message (very helpfully) tells us that error 229
is "too few arguements".
We read the article "Registry Entries (Visual FoxPro ODBC
Driver) which lists the registry details.
When we checked it, our machine had
API Level REG-SZ "0"
but the "0" should have been a "1".
Every other entry line appeared to be perfect.
So we changed it to "1" and re-booted and built a new ODBC
source and relinked and guess what!
Yep. Same old error.
We downloaded the latest Win2K patches and MDAC (2.7) but
all to no avail.
What are we doing wrong.
A colleague at a different site with a similar machine and
settings can run this query perfectly.
PLEASE!!! What are we doing wrong?
Regards
Robin Donald