Strange "unspecified error" in D7/Access query

I have a D7 app with an MS Access database, using ADO. In one of the tables
is a text field called Position, and in the app I run the following query
using a TADOQuery object:
select sum(profit) from trades where position="long"

This query results in an "Unspecified error" message (which is an OLE error)
when opened, and so does every other query referring to the Position field.
All other queries run without any problem. I suspected that for some reason
the field name was a problem, and when I changed it to TradePosition
everything was fine.

I wonder if anyone knows why that field name would cause a problem.

Glenn


.

Relevant Pages

  • Cancel Query from ADO
    ... Is there a way to cancel a long running query from ADO? ... The query runs for several mins then the user clicks on the cancel button on the app. ...
    (microsoft.public.sqlserver.programming)
  • Re: Run ADO/OLE DB from a CD-R
    ... > I need to get my VB6 app. ... > installing any files onto the host machine, or making any registry entries of ... > also have had Visual Studio installed, however on all other machines, the ADO ... Do you mean the bound-control 'ADODC' when you say 'ADO control'? ...
    (microsoft.public.data.ado)
  • Re: How much time does a query take?
    ... not only the MSDE running, but also a visualisation for a part of a ... tell our app when a fault occured und when it went away. ... the app would execute a query against the database to retrieve the ... Like I wrote in my first question, in that way there can be a query every ...
    (microsoft.public.sqlserver.msde)
  • Re: SQl Data Provider Performance Issues
    ... Can you provide a complete sample app ... selects with a single inner join perforn OK. ... When I run the query from SQL ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: Problem with an ADO query against SQL Server
    ... Debugging a hung app on the client side is another story... ... >>Use SQL server profiler to find out what "actually" is going on with SQL ... >>Server times out the query. ... >>> Or, was my program waiting somehow, for a response to the first query ...
    (microsoft.public.vb.database.ado)