Re: Problems with Runtime 2007

Tech-Archive recommends: Fix windows errors by optimizing your registry

Two things you can do to help troubleshoot the prob. Add error handling in
this procedure and make sure the msgbox shows the error number and
description, like this:

MsgBox Err.Number & vbCrLf & Err.Description

Sometimes you don't get an error message, but if you do it should help narrow
down what's going on.

2nd, to speed up testing you can test under (mostly) Access runtime
conditions with the retail version of Access. (At least you could in Access
2000 through 2003. I'm not positive about Access 2007 yet.) Make a shortcut
to open the db with the /runtime switch. Like this (all one line in the
target):

"C:\Program Files\Microsoft Office\OFFICE12\msaccess.exe" "C:\db1.mdb"
/runtime

That way you won't have to jump back and forth between two PCs that are
configured differently while you're testing your app. You won't be wondering
about missing references, because if the references for the db are good
*without* the /runtime switch on a certain PC, they'll be good *with* it.


Chris
Microsoft MVP


Nutcroft5 wrote:
Hi Chris

Thanks for responding...i think it's the FileSystemObject that is failing as
it doesn't even get to opening the email bit. I wondered if it was a
reference issue? I had to download Visual Basic for one of the bits of code
i put in but I have been developing this database for so long i can't
remember if it was this one!

It's hard to make suggestions for troubleshooting when there's no error
message or discription of which part is failing.
[quoted text clipped - 53 lines]

Kill ("c:\FileName.txt")

--
Message posted via http://www.accessmonster.com

.

Relevant Pages

  • Re: "There is an invalid use of the . or !" -version problem
    ... Did I miss where you described what the MsgBox was displaying for an ... >I've examined the references as they are identical in both environments. ... >uncovering the Database window... ... > Exit Sub ...
    (microsoft.public.access.gettingstarted)
  • Re: code no longer working
    ... references, they are all the same, and none are missing. ... Decompiling the DB. ... MsgBox "Sorry, ...
    (microsoft.public.access.formscoding)
  • Re: Error 5 on button-click in Access 2003
    ... > If it still does not work, it has to be an issue with references. ... rather than allenbrowne at mvps dot org. ... >> Exit Sub ... >> and an empty Visual Basic window on dismissing the MsgBox. ...
    (microsoft.public.access.forms)
  • Variable references
    ... I read in other posts that there are no references in VBScript - ... If I were to do this to display "fld1", ... Msgbox fld1.Value ...
    (microsoft.public.scripting.vbscript)