You could of course explain what is the problem you are having (most often
due to the fact that the Jet Expression Service exists for RunSQL but not
for Database.Execute, which allows you to have expressions using form
controls and such), but occasionally there are the concurrency issues that
are assisted by things like the dbSeeChanges constant.
But if you post a generic message like this one that has no actual content
other than a pointer to an old thread and an announcement that the issue is
dead for you, then it is unclear how you expect people to respond?
--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies
This posting is provided "AS IS" with
no warranties, and confers no rights.
"DCM Fan" <dc****@aol.comSPNOAM> wrote in message
news:20***************************@mb-m20.aol.com...
All,
A month or so ago I started a thread titled "I was *forced* to use
RunSQL."
At that time, I said I'd get back to you after trying the dbSeeChanges
constant in the Execute method. I was very confident that it was going to solve the
problem.
It didn't. I've resigned myself to using RunSQL instead of dbs.Execute in
this context...first time ever. The bottom line from the JET lovers in here is
that my code is messed up somewhere (understandably). Of course, I'm blaming
JET! :)
I'm not going to post the entire module in this newsgroup, but if someone
really wants to see ALL of the code in context, send me email to the
address in here, and I'll be happy to send a response email with module text intact.
Otherwise, I consider the issue dead.