Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Run-Time Errror '2004' on Access

Status
Not open for further replies.

breslinc

Technical User
Oct 7, 2002
22
US
Help!!!

I have set up a database where I can email out the results to multiple people using outlook. Once I try to send the results out after more than 3 sends, i get a run-=time error '2004'.

I have never seen this on such a small database with a small amount of data running thru it. What can i do?


Thanks
Chris
 
Do you get an associated description with the error number. Can you provide more detail. I've tried a Google search and it yields a couple of interesting things you could follow up on, though they may not be related to your problem.

Try:


Which details an error 2004 relating to a memory problem. It in turn refers to a microsoft knowledge base article q253912, at:


which you can check out.

The Microsoft Access error # 2004 description is: "Application-defined or object-defined error", as distinct to the memory error above, so without any further elaboration on your part, its hard to provide further help.

You might get lucky with the info above,

Keep us informed,



Steve Lewy
Solutions Developer
steve@lewycomputing.com.au
(dont cut corners or you'll go round in circles)
 
Application-defined or object-defined error

A bit off-topic perhaps, but lots of errors fall into this category. However, at runtime after the error has occured, you can type "
Code:
print err.description
" in the debug window and see the real description.

Best regards
 
Well... i appreciate allt he posts but the problem still is here. The only thing that is running is access.
 
Do you have create/open object variables? Applications, recordsets, connections, anything that is instatiated with Set? I assume you have some Outlook objects...

If yes, make sure you Set them to Nothing as soon as you're done with them:

Set ObjVar = Nothing

Compile your code as soon as you've made any change.
Compact and repair the database on a regular basis

If no success, create a brand new database and import all objects.
If still no success, back up the database and try the decompile switch:

Start - Run
msaccess.exe /decompile "C:\Path\YourFile.mdb"

HTH


[pipe]
Daniel Vlas
Systems Consultant

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top