Re: RecordSet fails if a field is null ! - unspecified error '80004005'

On Wed, 31 May 2006 22:07:42 -0400, "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx> wrote:

OK, I asked you what the datatype of the origin field was and you did not
understand the question. So I will ask again: what type of data is stored in
origin? Text or numbers?

ha, yes I completely missed to question the first time. Origin is a text field.


Actually, it doesn't matter. There is nothing about a null being returned
that should cause an error when you open a recordset.

Are you sure it's the rs.open line? Have you temporarily, for debugging
purposes, put a response.end statement on the next line after the open
statement to see if the error still occur?

Yeah thats what I was doing to be sure. This is a really strange problem that is going to bother me for a few weeks. While i was
troubleshooting (and going in circles) I some how fixed the problem. I noticed that some of the fields where named poorly such as "where",
which should cause my sql to have bad syntax.. For the life of me I cannot see what the problem was with the origin field (and while
testing that was the only field i was selecting)...

Who knows... I'm sure i mad a typo somewhere.. i'll just never know what it was


If you are sure about the open statement raising the error, then I have to
start grasping at straws. Could your database be corrupt? There are database
utilities in Access that you can use to compact and repair your database.
Give that a try.

Maybe something is wrong with your Jet components. Go to microsoft.com and
search for the latest Jet 4.0 service pack (you should probably ask in an
Access group for pointers to that).

Are you using the Jet OLE DB provider in your connection string? Or the ODBC
driver? Switch to the one you are not using to see if that makes a
difference.

Good idea. I didnt think you could use ODBC with access... then again, why not.
.

Relevant Pages

  • Re: ADO.net Code contest
    ... Ah, actually, accessing an Access database is done through JET. ... generic interface like OLE DB or ODBC from any data access interface ... ODBC, OLE DB are ...
    (microsoft.public.dotnet.framework.adonet)
  • Re: Replacement for Dao
    ... then open both and fetch from the database. ... Jet Engine to be deprecated soon - in fact Jet will not be available at all ... > that Jet actually provides ADO support through its ODBC (I am still ... > was straight forward in Dao) and hence ODBC may perform better than ADO. ...
    (microsoft.public.vc.database)
  • Re: ODBC(No column properties collection) vs Jet (alphabet ordering)
    ... ADOX relies on a provider's capabilities to return ... about the database objects, because Jet was designed for Access itself. ... it was designed as a layer between ADO and ODBC driver. ...
    (microsoft.public.data.ado)
  • Re: accessing ms access via ODBC without Microsoft Access
    ... ODBC connection to a .mdb file - can I still access the 'database' via ... What you cannot do is to access a Jet database via ... Microsoft Access MVP ...
    (comp.databases.ms-access)
  • Re: Nameless CREATE
    ... The starting point is either an existing database or one that is ... "Describe" involves issuing an SQLDescribeCol function to ODBC ... essentially much the same as character data type apart from all 8 bits ... ALTER TABLE tablename ADD COLUMN BinaryColumn BINARY ...
    (comp.lang.forth)