Re: Limitations using Developer
- From: "Chris Mills" <phad_nospam@xxxxxxxxxxxxxx>
- Date: Sun, 14 Aug 2005 19:18:48 +1200
The packaging wizard is just what you use to install it. There are better
packagers like www.sagekey.com, but that's just installation minutiae.
Access Runtime is what the user ends up with (however it is installed).
The list of what doesn't work in Runtime vs Full Access is quite extensive.
I'm not sure where there's a comprehensive list. You can test your app in the
runtime environment by placing /Runtime on the startup command line on your
development machine.
(basically, better have full error-handling otherwise it goes belly-up, custom
menu/toolbars, no form filters write your own, no design-mode/nothing in the
menus except what you allow. Some design-type stuff can be done in Runtime
just they have to be done in code because it's the user interface that's
disabled (the database window) )
There's really not much you can't do. Just you have to do it a different way
(through automated macros or code). You'll soon find out with the /Runtime
switch, and it's not that big a deal. Think...the only things the user can do
is what you write/allow them to do, they can't do anything else.
Oh alright then :-)
http://support.microsoft.com/default.aspx?scid=kb;en-us;208730
ACC2000: Differences Between Retail and Run-Time Microsoft Access
(will be similar for later versions)
Chris
"cottage6" <cottage6@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> My company is in the middle of a conversion from Lotus products to MS
Office.
> I need to rewrite an old complicated Approach file to Access (Access 2000).
> I'm not very advanced in my Access knowledge yet and have only used the
> packaging wizard (XP Developer) once to get a database to a user who didn't
> have Access. If I remember correctly, after the database got to the user
> there were some things she couldn't do that I was able to when I created the
> database. Sorry I can't quite remember what they were; it's been awhile.
> Anyway before I start the rewrite on this I'd like to know what I can't
> expect a user to have in a database using the packaging wizard, versus
> installing Access on the user's PC. It's always a possibility I did
> something wrong to begin with. Any feedback would be great. TIA.
.
- Follow-Ups:
- Re: Limitations using Developer
- From: cottage6
- Re: Limitations using Developer
- References:
- Limitations using Developer
- From: cottage6
- Limitations using Developer
- Prev by Date: Re: Finding a single value in a table
- Next by Date: Re: Limitations using Developer
- Previous by thread: Limitations using Developer
- Next by thread: Re: Limitations using Developer
- Index(es):
Relevant Pages
|
