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

 

[ruralguy via AccessMonster.com]

What is the EXACT line that fails? Since DATABASE is a reserved word, I would
hope that is not what you have. Does the target machine have all of the OS
and Office 2007 Updates and HotFixes applied?

 

[Linq Adams via AccessMonster.com]

Also, when apps run fine on one machine and not on another or run fine in one
version and not when run under another version, the first thing you have to
think about are missing references.

Here are Doug Steele's detailed instructions on how to troubleshoot the
problem:

http://www.accessmvp.com/DJSteele/AccessReferenceErrors.html

 

[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...

 

[ruralguy via AccessMonster.com]

Every release of Access gets a little more critical of some issues while
introducing some new quirks. Glad you were able to pin it down.

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...

What is the EXACT line that fails? Since DATABASE is a reserved word, I would
hope that is not what you have. Does the target machine have all of the OS

[quoted text clipped - 14 lines]

 

[ruralguy via AccessMonster.com]

I know you know that Date is a reserved word and not to be used as a field
name even though the {Date] brackets should solve that particular issue. What
you had as a query looks like it should work to me.

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...

What is the EXACT line that fails? Since DATABASE is a reserved word, I would
hope that is not what you have. Does the target machine have all of the OS

[quoted text clipped - 14 lines]

 

[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.

 

[AccessVandal via AccessMonster.com]

Date() is a Function which will never work in your SQL string in VBA. The
correct method would be.

"INSERT........VALUES (101,59, 101, 1," & Date() & ")"

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.

snip..

 

[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.

 

[AccessVandal via AccessMonster.com]

The others have pointed out to uncheck and re-check the References. Something
might have mess-up your Access database. Incorrect VBA SQL syntax is one of
them, I've encountered this problem before. Have you compile the code and do
a Compact and Repair?