Re: Still Getting Runtime Error Message
From: Albert D. Kallal (PleaseNOOOsPAMMkallal_at_msn.com)
Date: 08/04/04
- Next message: Ed the Redhead: "Subroutine basics"
- Previous message: Christopher: "Re: Still Getting Runtime Error Message"
- In reply to: Chaplain Doug: "Re: Still Getting Runtime Error Message"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 3 Aug 2004 19:50:42 -0600
"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.
That is ok. I always distributed a mde, as it ensures that the application
has
no compile errors, and prevents tampering (in fact, often I have provided
the "source" in a separate dir when users request this). However, it is
just fine to provide a mdb as you do, but mde are preferred as they stay
compiled and are some what smaller in size, and can be more stable.
> 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?
Yes, you got the right idea as above. Often, I just use WinZip.
However, you can just package the mdb file with the wizard
and have it "overwrite" the front end (of course, now if you
are going to "overwrite" the old FE, then the users will
loose any changes they made to their mdb FE (so, keep
this in mind, since you do distribute a mdb to allow changes,
but now users will loose their changes. I am not sure how
you will manage this problem).
Regardless, you don't need to include the runtime part, but just the mde (or
mdb in your case).
> Can this be done if the user does not have
> MSAccess on their system (and thus are using the runtime)?
Yes, I do this all the time. However, you should provide some means to
re-link the tables. Generally, after some time of building applications, you
will have in your tool box of goodies some code cobbled together to re-link
the tables. Even for my users that have the full version, it rather too much
to ask end users to learn and figure out how to use the linked table
manager. So, a good setup will provide some re-linking ability anyway.
(in case the location of the back end needs to be changed for
example).
Since you are using the runtime, then users don't have the
general ms-access tools available (nor should they need them!!!). So, what
most of us do is grab the following code and build our own re-link
system:
http://www.mvps.org/access/tables/tbl0009.htm
>
> 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.
Good for you. Testing is one of those things we hate, but must
do!
Virtual PC as mentioned is really nice, since you can roll back
any changes to a session (thus, I can install the runtime, install my
stuff, test it, and then say.....you know all that stuff I just
did......un-do it!). This is dream for developers. Further, not only can you
create a imaginary pc, but you can create several and even network them
together....all occurring inside of one pc. Once again, for testing updates,
or any kind of software that needs a network and a few computers...you can
do
this right on your single pc, and not have to go out and setup multiple pc's
to do this. So, Virtual PC is a software product you purchase. On my windows
xp notebook, I can run a copy of windows 98, and windows xp in a "window".
These "windows" are each their own little computer. Not saying you need
Virtual pc..just saying they are great for testing...
http://www.microsoft.com/windows/virtualpc/default.mspx
> 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.
When you say reference, do you just mean some code that runs the pdf file,
or do you mean tools->references? If you mean that you set a reference in
the
VB IDE to the pdf system, then that would be source of breakage here. If any
pc you install to does NOT have the same version and exact same install of
the PDF, then you will suffer a breakage. If you are talking about some
code that simply opens, or shells out, then you don't have to worry.
-- Albert D. Kallal (Access MVP) Edmonton, Alberta Canada pleaseNOOSpamKallal@msn.com http://www.attcanada.net/~kallal.msn
- Next message: Ed the Redhead: "Subroutine basics"
- Previous message: Christopher: "Re: Still Getting Runtime Error Message"
- In reply to: Chaplain Doug: "Re: Still Getting Runtime Error Message"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
