Getting a "Reserved Error 3099"

[Andrea]

Hi
I've developed an application and deployed in an ACCDR format.
First of all this format generates a lot of errors in Vista/Windows 7 and it
works fine in XP. I have been forced to release the ACCDB to Vista/W7 users.
But now both the ACCDB and ACCDR versions shows this error during a valid
and legitimate call "database.execute(sql string)". That sql command is
correct and works fine, but on that machine I see
"Error Number 3000: Reserved Error (-3099); there is no message for this
error"

This is really annoying since I don't know what's wrong and most importantly
it happens only on that PC.

Do you have any idea? Thanks

 

[Andrea]

Thanks for the answer Ruralguy.
The issue was that, on that specific machine, the call
INSERT INTO tbl_milestone (Person,IDProgram,RefMilestone,Status,[Date])
VALUES (101,59, 101, 1, date())

Did not work (with that silly error).
When I replaced the "date()" with a proper date, it worked.

Access is really bad for debugging. I had these "unclear" issues on Access97
and they're still present in access 2007, 10 years later...

 

[John W. Vinson]

INSERT INTO tbl_milestone (Person,IDProgram,RefMilestone,Status,[Date])
VALUES (101,59, 101, 1, date())

Did not work (with that silly error).
When I replaced the "date()" with a proper date, it worked.

This appears to be the very common References bug. Open any module in design
view, or open the VBA editor by typing Ctrl-G on the machine exhibiting this
problem. Select Tools... References from the menu. One of the .DLL files
required by Access will probably be marked MISSING. Uncheck it, recheck it,
close and open Access.

If none are MISSING, check any reference; close and open Access; then uncheck
it again. This will force Access to relink the libraries.

 

[Andrea]

Date() is a Function which will never work in your SQL string in VBA.

Sorry, but that query was working and works on about 10 different PC. Only
on that specific PC was causing issues.

And even if so, I would expect Access to say that, instead of saying
"Internal error".

 

[David W. Fenton]

Sorry, but that query was working and works on about 10 different
PC. Only on that specific PC was causing issues.

And even if so, I would expect Access to say that, instead of
saying "Internal error".

When the references are screwed up (which seems like the likely
problem here, as the symptoms are the classic ones), it's impossible
for Access to resolve the error number because the code itself is
unable to run.

Avoid using anything other than the 3 base references, Access, DAO
and VBA.