Re: Still Getting Runtime Error Message
From: Christopher (NoSpamThanks_at_spam.com)
Date: 08/04/04
- Previous message: M.L. Sco Scofield: "Re: Office 2003 Developer"
- In reply to: Chaplain Doug: "Re: Still Getting Runtime Error Message"
- Next in thread: Albert D. Kallal: "Re: Still Getting Runtime Error Message"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 4 Aug 2004 08:14:13 +0800
I am still learning as well - but this my help.
a. If you are using the Run Time, I believe that it is not pobbile for the
users to change the design of reports etc. To do this, they need a full
evrsion of Access.
b. Front End and back End is the best way to go.
c. To Check References, did you go to Modules then Tools References?
Oh, I suggest setting up error trapping in every bit of VBA code - there is
an add in supplied with my developer ed that makes this easy.
Christopher
"Chaplain Doug" <anonymous@discussions.microsoft.com> wrote in message
news:b96101c47997$13aa7fa0$a301280a@phx.gbl...
> To answer your questions and to ask a couple more:
>
> 1. I am packaging the .mdb (or at least telling the
> package wizard to package the .mdb). I want the user to
> have the flexibility to get to the reports, etc. if they
> need to. This leads to another question. I will likely
> be sending updates to the software (forms, reports,
> etc.). Is there any problem with packagaing the db as a
> frontend and backend so that I may jusat send updates to
> the frontend? Can this be done if the user does not have
> MSAccess on their system (and thus are using the runtime)?
>
> 2. I do not know how to set up a virtual PC. However,
> my "mule" is a pc that does not have Access installed. I
> have other "mules" that have Access 2002 and Access 2003.
>
> 3. There are not any references to other MS products
> (like Excel, Word, etc.). The only reference to an
> external program is to an Adobe PDF file that brings up
> Adobe Reader.
>
>
>
> >-----Original Message-----
> >You as a general rule should put error handling in most
> routines. A
> >un-handled error in the runtime simply quits ms-access.
> >
> >(you are using a mde...right?)
> >
> >As mentioned, the first thing to try is installing ms-
> access on that machine
> >that fails. And, really, for any software developer you
> do need a test mule,
> >or even better is something like virtual pc. (virtual pc
> is a pc that runs
> >"inside" of windows, and thus you can test software
> installs).
> >
> >The first thing you need to check is if you any
> references, or automaton
> >code (that is code that uses Excel, Word, Outlook etc).
> If you use ANY of
> >these applications, then you need to use what is called
> late binding (this
> >means to remove the references you have in tools-
> >references to the other
> >office programs).
> >
> >Also, when you say you get a runtime error...is this at
> startup, or when you
> >use a particular option/feature of your software? Also,
> are the installs on
> >the problem pc's being done with full admin rights, or
> restricted user
> >rights?
> >
> >Also, when you find a pc that fails, then un-install your
> software, install
> >JUST ms-access (full version), and then try running your
> full mdb file (not
> >the mde) (of course, don't use the runtime switch). This
> will usually let
> >you see and trap what the error was.
> >
> >However, you can NOT even begin to possibility test your
> install stuff on
> >your developer pc? I mean, I been installing software for
> days on end on my
> >pc, and it has got just about everything including the
> kitchen sink
> >installed. If your software needs ANY of the zilling
> billion things that
> >have been installed on your development pc over time,
> then deploying to a
> >clean pc will fail due to some dependence you have
> on "one needle" in the
> >haystack. Thus, as a rule, testing your packaged install
> on your development
> >pc is a complete waste of time, as it only proves that
> you incredible
> >development box with all the huge amount of developer
> tools allows your
> >software to run....and that is not what you want to test
> at all! (you learn
> >nothing by doing this!). Even doing a test runtime
> install on a "mule" pc
> >means now that you changed things on that pc from what a
> new user will see.
> >So, even testing over and over on a test mule is not
> good. You need a
> >"clean" install of windows each time. (you can use Ghost,
> or as mentioned
> >even better is Virtual pc, as it has roll back ability).
> >
> >So, if you use any other part of the office system
> (graping, Excel, Word
> >etc) with the runtime, then that is the first obvilues
> area. Even if you
> >don't, then remove all un-necessary references in your
> sfotware. Here is
> >some reading on this subject:
> >
> >Allen Browne
> >http://users.bigpond.net.au/abrowne1/ser-38.html
> >
> >Doug Steele:
> >http://members.rogers.com/douglas.j.steele/AccessReference
> Errors.html
> >
> >Peter Walker:
> >http://www.papwalker.com/dllhell/index-page2.html
> >
> >
> >MsKb Articles: 310803, 208218, 209849, 286300
> >
> >ACC2000: How Access 2000 Resolves Visual Basic for
> Applications References
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;248941
> >
> >ACC2000: How to Resolve Reference Issues in an Access
> Database
> >http://support.microsoft.com/default.aspx?scid=kb;en-
> us;310803
> >
> >
> >.
> >
- Previous message: M.L. Sco Scofield: "Re: Office 2003 Developer"
- In reply to: Chaplain Doug: "Re: Still Getting Runtime Error Message"
- Next in thread: Albert D. Kallal: "Re: Still Getting Runtime Error Message"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
