MartyConnelly
martyconnelly at shaw.ca
Mon Dec 22 12:00:03 CST 2003
That asp error is a server error that may be indicative of (a) a badly overloaded web server, or one without enough RAM (where it is pounding on the Windows swap file, and thus taking forever to serve up pages) (b) a script with an infinite loop somewhere that never finishes. perhaps bad choice of keywords. Active Server Pages (web pages with an .ASP file extension) have 90 seconds to complete unless the server admin specifies say Server.ScriptTimeout = 999 seconds I saw in the archives a reference to code that checks the references. Will this work in an MDE also? Probably only if this is the first piece of code executed on entry to the mdb say via an autoexec macro see http://www.trigeminal.com/usenet/usenet026.asp?1033 As a temporary work-around, will having her open another MDB, setting a new reference, exiting, then going back into references and un-checking the just set reference correct her problem in the MDE? Or are the references specific to a database? The references are specific to the mde You might try late binding the library or dll called in the MDE Bobby Heid wrote: >I have a little back-log of e-mail from AccessD and after submitting this >question, I save an e-mail saying to search the archives for "Broken >References in Runtime AXP and A97". > >When I do, I get the following error message: >------------------------- start of message >-------------------------------------- >Active Server Pages error 'ASP 0113' > >Script timed out > >/AccessD/default.asp > >The maximum amount of time for a script to execute was exceeded. You can >change this limit by specifying a new value for the property >Server.ScriptTimeout or by changing the value in the IIS administration >tools. >------------------------------ End of message >----------------------------------- > >I got this on Friday and today. I tried the search string in quotes and >without. Is there a problem with searching the archives? > >Thanks, >Bobby > > >Subject: [AccessD] Error 3075 - Function is not available in expressions in >queryexpression. > > >Hey, > >A user is getting the above error message in an ACC XP MDE. I know that it >has something to do with references. I also know that you cannot refresh >references manually in an MDE. > >I saw in the archives a reference to code that checks the references. Will >this work in an MDE also? > >As a temporary work-around, will having her open another MDB, setting a new >reference, exiting, then going back into references and un-checking the just >set reference correct her problem in the MDE? Or are the references >specific to a database? > >Thanks, >Bobby > > > -- Marty Connelly Victoria, B.C. Canada