docmd.runSQL fails on Windows 2000 
Author Message
 docmd.runSQL fails on Windows 2000

I am having a problem where a program that I wrote that uses a lot (a whole
lot...) od DoCmd.RunSQL statements keeps failing on computers using Windows
2000 Professional.  If you take the same SQL and define a QueryDef there are
no problems (except for the hours of rewriting for me..)  I was wondering if
anyone else had encountered this problem, and had possibly found a way
around it.  (Access 97 on Windows 2000)  As far as I can figure, it is a
problem with permissions, because their are no permissions assigned to a
simple SQL statement, but there are to a QueryDef object. Any thoughts would
be greatly appreciated.


Wed, 09 Jun 2004 01:47:26 GMT  
 docmd.runSQL fails on Windows 2000
Hmm, what error you get with .RunSQL?


Quote:
> I am having a problem where a program that I wrote that uses a lot (a
whole
> lot...) od DoCmd.RunSQL statements keeps failing on computers using
Windows
> 2000 Professional.  If you take the same SQL and define a QueryDef there
are
> no problems (except for the hours of rewriting for me..)  I was wondering
if
> anyone else had encountered this problem, and had possibly found a way
> around it.  (Access 97 on Windows 2000)  As far as I can figure, it is a
> problem with permissions, because their are no permissions assigned to a
> simple SQL statement, but there are to a QueryDef object. Any thoughts
would
> be greatly appreciated.



Wed, 09 Jun 2004 04:58:00 GMT  
 docmd.runSQL fails on Windows 2000
Actually, Access generates some error log and quits.  I have yet to see this
error log (two users are having the problem, and I haven't had a chance to
do very much testing on it myself.)

Thanks.
Dylan.

Quote:
> Hmm, what error you get with .RunSQL?



> > I am having a problem where a program that I wrote that uses a lot (a
> whole
> > lot...) od DoCmd.RunSQL statements keeps failing on computers using
> Windows
> > 2000 Professional.  If you take the same SQL and define a QueryDef there
> are
> > no problems (except for the hours of rewriting for me..)  I was
wondering
> if
> > anyone else had encountered this problem, and had possibly found a way
> > around it.  (Access 97 on Windows 2000)  As far as I can figure, it is a
> > problem with permissions, because their are no permissions assigned to a
> > simple SQL statement, but there are to a QueryDef object. Any thoughts
> would
> > be greatly appreciated.



Wed, 09 Jun 2004 06:03:09 GMT  
 docmd.runSQL fails on Windows 2000
Hmm, do your SQL based on queries? then probably some query get corrupted.
the try to recreate it

--
Alex Dybenko
http://Alex.Dybenko.com


Quote:
> Actually, Access generates some error log and quits.  I have yet to see
this
> error log (two users are having the problem, and I haven't had a chance to
> do very much testing on it myself.)

> Thanks.
> Dylan.


> > Hmm, what error you get with .RunSQL?



> > > I am having a problem where a program that I wrote that uses a lot (a
> > whole
> > > lot...) od DoCmd.RunSQL statements keeps failing on computers using
> > Windows
> > > 2000 Professional.  If you take the same SQL and define a QueryDef
there
> > are
> > > no problems (except for the hours of rewriting for me..)  I was
> wondering
> > if
> > > anyone else had encountered this problem, and had possibly found a way
> > > around it.  (Access 97 on Windows 2000)  As far as I can figure, it is
a
> > > problem with permissions, because their are no permissions assigned to
a
> > > simple SQL statement, but there are to a QueryDef object. Any thoughts
> > would
> > > be greatly appreciated.



Wed, 09 Jun 2004 16:39:48 GMT  
 docmd.runSQL fails on Windows 2000
BTW I would get rid of all Docmd.RunSQL as per
www.ssw.com.au/SSW/KB/KBAnswer.asp?KBNumber=Q647176&searchFor=docmd

Adam


Quote:
> I am having a problem where a program that I wrote that uses a lot (a
whole
> lot...) od DoCmd.RunSQL statements keeps failing on computers using
Windows
> 2000 Professional.  If you take the same SQL and define a QueryDef there
are
> no problems (except for the hours of rewriting for me..)  I was wondering
if
> anyone else had encountered this problem, and had possibly found a way
> around it.  (Access 97 on Windows 2000)  As far as I can figure, it is a
> problem with permissions, because their are no permissions assigned to a
> simple SQL statement, but there are to a QueryDef object. Any thoughts
would
> be greatly appreciated.



Fri, 11 Jun 2004 05:54:35 GMT  
 
 [ 5 post ] 

 Relevant Pages 

1. DoCmd.RunSQL

2. DoCmd.RunSQL Error

3. DoCmd.RunSQL error 2

4. docmd.RunSql problem

5. docmd.RunSQL String Concatenation

6. DoCmd.RunSQL too long record

7. DoCmd.RunSQL

8. suppress warnings on DoCmd.RunSQL ?

9. docmd.runsql repeat problem

10. docmd.runsql help required

11. DoCmd.RunSQL vs. Recordsets

12. Quick syntax question on - DoCmd.RunSQL

 

 
Powered by phpBB® Forum Software