|
Home > Archive > FoxPro Help and Support > May 2005 > Re: Column '' is not found (error VFP 1806 - VB: -2147217900)
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Column '' is not found (error VFP 1806 - VB: -2147217900)
|
|
| Dan Freeman 2005-05-10, 11:24 am |
| Hmmm .... that error message gives the name of the column the query is
looking for.
That the name is empty may mean that your software is passing an empty
string in the field list. Are you certain that isn't the case? Can you log
the query you passed that generates this error and post it?
Dan
David wrote:
> Hi,
>
> I am using Visual Basic 6 with ADODB, Visual FoxPro 7.0.
>
> I have a strange error that I do not understand. Also, I did not find
> any ways to reproduce the problem. It just happen after my software
> runs for a certain time.
>
> I ouput the error from Visual Basic 6.0 and here what I found:
>
> VB Error # -2147217900
> Generated by Microsoft OLE DB Provider for ODBC Drivers
> Description [Microsoft][ODBC Visual FoxPro Driver]SQL: Column ''
> is not found.
>
>
> After searching a solution to that problem, I found that the error
> from Visual Fox Pro is:
>
> 1806 SQL: Column "field | variable" is not found.
>
>
http://msdn.microsoft.com/library/d..._a_
z.asp
>
> Unfortunatly the link does not work!
>
> It seems the problem does not affect to much my software, but because
> I log all the errors into a file, it waste my log file.
>
> Please help me!!!!
>
> David
| |
| David 2005-05-10, 11:24 am |
| If the software is passing an empty string, I should have the error all the
time, no? Those functions that generate the error are called very often.
For the SQL strings, here how they look like:
UPDATE routerlns SET Monitor=3 WHERE routnum=4
SELECT interval FROM user
SELECT maintgr FROM spulns WHERE maintgr=1 and deleted=0
SELECT op_pass, sch_pass, diag_pass, spuid FROM maint WHERE spuid=97
"Dan Freeman" wrote:
> Hmmm .... that error message gives the name of the column the query is
> looking for.
>
> That the name is empty may mean that your software is passing an empty
> string in the field list. Are you certain that isn't the case? Can you log
> the query you passed that generates this error and post it?
>
> Dan
>
> David wrote:
> http://msdn.microsoft.com/library/d..._a_
z.asp
>
>
>
| |
| Dan Freeman 2005-05-11, 1:24 pm |
| When I'm facing an error message that I'm unclear about, I first try to
think how I might cause that error message if I wanted to cause it
intentionally. Then I go looking for where/how I might be causing it. That
was the point of my last response.
I really don't have anything to suggest beyond the obvious, which is that
sometimes you're passing an empty string. <shrug>
There are, of course, times when the error message is EXACTLY accurate but
still uninformative. This may be one of those times.
Dan
David wrote:[color=darkred
]
> If the software is passing an empty string, I should have the error
> all the time, no? Those functions that generate the error are called
> very often.
>
> For the SQL strings, here how they look like:
>
> UPDATE routerlns SET Monitor=3 WHERE routnum=4
> SELECT interval FROM user
> SELECT maintgr FROM spulns WHERE maintgr=1 and deleted=0
> SELECT op_pass, sch_pass, diag_pass, spuid FROM maint WHERE spuid=97
>
> "Dan Freeman" wrote:
>
http://msdn.microsoft.com/library/d..._a_
z.asp[color=darkred]
| |
|
| I understand your point (about the empty string). I just cannot get that even
if I print the SQL string, I always have something in it.
Thanks anyway. I just hope that other people will have a look to that
problem and will help us! :-)
"Dan Freeman" wrote:
> When I'm facing an error message that I'm unclear about, I first try to
> think how I might cause that error message if I wanted to cause it
> intentionally. Then I go looking for where/how I might be causing it. That
> was the point of my last response.
>
> I really don't have anything to suggest beyond the obvious, which is that
> sometimes you're passing an empty string. <shrug>
>
> There are, of course, times when the error message is EXACTLY accurate but
> still uninformative. This may be one of those times.
>
> Dan
>
> David wrote:
> http://msdn.microsoft.com/library/d..._a_
z.asp
>
>
>
|
|
|
|
|