Re: Error 3265 mystery error
- From: "Bob Barrows [MVP]" <reb01501@xxxxxxxxxxxxxxx>
- Date: Mon, 26 Jun 2006 13:38:27 -0400
will f wrote:
The environment is VB6.
I'm not using ADOX in the app. I just created an ADOX Catalog object
as part of my debugging to see if ADOX would see the table.
I did check the database window in MS Access, and the table is there.
I'll check out the link you sent me regarding Jet Delayed-Write --
I'm not familiar with it.
It's not relevant. It might have been relevant if this was a dynamically
created table.
I'm more inclined to go with the "reserved keyword" theory: check your
field names against the list of reserved words in that link I cited.
If it's not a reserved keyword issue, then try exporting your table to
another database and see if it can be opened in the test database. If it
can, then we have a "corrupt database" issue. If not, send me the test
database via email and I'll see if i can reproduce your error.
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.
.
- 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
- 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: Large varchar columns with SQL server
- Previous by thread: Re: Error 3265 mystery error
- Next by thread: Re: Error 3265 mystery error
- Index(es):
Relevant Pages
|
|