Re: Error 3265 mystery error
- From: "Stephen Howe" <stephenPOINThoweATtns-globalPOINTcom>
- Date: Mon, 26 Jun 2006 18:10:16 +0100
So that 3265 seems to be behaving as if I am referencing a field that does
not exist in the table. But, as you can see, I am not specifically
referrencing any fields at all.
But you are - indirectly that is.
If you do "SELECT * FROM tblTest", a meta-data lookup on tblTest has to
occur to find the fields that correspond to "*".
As far as the recordset being properly initiated, when I change "tblTest"to
some other table in the database, it opens fine.the
Also, I have run a database compact/repair on the database before doing
whole operation, so I don't think the db is corrupted - but I could be
wrong.
Any ideas?
Well yes. More information
1. Version of MDAC installed.
2. I would check to see what version of the Jet Provider you have installed
and make sure it is the latest - it no longer comes with MDAC. You need to
install seperately
3. Some checking on your Access databases. Is this one the same version as
the others?
To me, it looks like a database corruption issue or possibly configuration
issue.
Cheers
Stephen Howe
.
- References:
- Error 3265 mystery error
- From: will f
- Re: Error 3265 mystery error
- From: Bob Barrows [MVP]
- Re: Error 3265 mystery error
- From: will f
- Error 3265 mystery error
- Prev by Date: Re: Error 3265 mystery error
- Next by Date: Re: Error 3265 mystery error
- Previous by thread: Re: Error 3265 mystery error
- Next by thread: Re: Error 3265 mystery error
- Index(es):
Relevant Pages
|
|