Re: MDE and runtime

Better yet...compile 2000 and don't worry about compiling in newer versions.

--
Paul Overway
Logico Solutions, LLC
www.logico-solutions.com


"Alex Dybenko" <alexdyb@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:OMkA$chVGHA.1348@xxxxxxxxxxxxxxxxxxxxxxx
Brian,
if your clients has versions 2000, xp, 2003 installed - then you have to
install at least Access 2000 and compile MDE using it.

Of course you can also install Access 2003 runtime at each PC. But... for
me is much less problems to ask client what Access version he has and
compile using proper version

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com


"Brian" <brainy@xxxxxxxxxxxx> wrote in message
news:%23KZTR7eVGHA.5916@xxxxxxxxxxxxxxxxxxxxxxx
Yes, but at this point I may be sending the app to clients with nothing
more than a "requires minimum of Access 2000, or else you must install
the included Access 2003 runtime". That is, I may be involved with
clients that simply want to purchase the software with none of my
involvement in (or even knowledge of) their infrastructure. It certainly
makes me look a lot less flexible and knowledgeable if I have to start
asking questions about their Access versions before I send them a demo
version. And since the app is still under development to some degree, I
may be issuing updates on a regular basis for some time to come.
Customers! They keep getting in the way of development... Now, if I could
just keep the customers away, I wouldn't have this problem, would I?

Is it feasible to simply require all clients to install the Access 2003
runtime package, or will that cause problems for those having
pre-existing Access 2002 or 2000on their computers?

I have Access 2003 with VB Tools, so I have no way to compile to an
earlier version. Or are you saying that I can just convert to Access 2000
format, and then compile MDE, and it will work?

"Alex Dybenko" <alexdyb@xxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:uPTifFYVGHA.4884@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
the trick is to compile MDE on a same Access version, then on a client
PC. Or, at least, you can compile on lowest version number

--
Best regards,
___________
Alex Dybenko (MVP)
http://alexdyb.blogspot.com
http://www.PointLtd.com


"Brian" <brainy@xxxxxxxxxxxx> wrote in message
news:O1Be7cNVGHA.1236@xxxxxxxxxxxxxxxxxxxxxxx
The Access Object Library reference (MSACC.OLB) is different for my dev
machine (Access 2003 with VB Tools), where this reference sits in an
...Office11 folder and clients having Access 2000 or 2002, where the
reference sits in the ...Office10 folder. Thus, my app fails miserably
as an MDE unless it is compiled on a machine having the earlier version
of Access.

Is there any way other than an MDE to keep the 99% of casual pirates
out? Never mind the other 1% that are serious hackers. MDB with
AllowBypassKey = False is too easy to undo; there are several tools
already available to turn this on again.

Is it feasible to simply push out an Access 2003 runtime with EVERY
implementation, or will this mess up existing settings or file
associations when installed on systems that have Access 2000 or 2002
full version installed? Could I even guarantee that the runtime would
be used for my app if I did it this way? (Yes, I do have the VB Tools
for Office and thus the developer tools).

Or, should I just distribute the Office11 Access Object Library to the
appropriate folder during installation so that even the Office10 folks
will have the file in the correct location for the reference.

Or...am I just stuck with having to copy the Office10 files to my hard
drive and changing the reference before compiling the MDE for those
having the earlier version of Access?







.

Relevant Pages

  • Re: MDE and runtime
    ... if your clients has versions 2000, xp, 2003 installed - then you have to install at least Access 2000 and compile MDE using it. ... Of course you can also install Access 2003 runtime at each PC. ... I may be involved with clients that simply want to purchase the software with none of my involvement in their infrastructure. ... Or are you saying that I can just convert to Access 2000 format, and then compile MDE, and it will work? ...
    (microsoft.public.access.devtoolkits)
  • Re: MDE and runtime
    ... old 2000 Pro CD and install it on my dev PC in order to accomodate this? ... install at least Access 2000 and compile MDE using it. ... the reference sits in the ...Office10 folder. ...
    (microsoft.public.access.devtoolkits)
  • Re: Compact SQL - Any CPU Build
    ... After the install, I confirmed the keys were created under ... our application can be installed on both of the x86 and x64 platform. ... But if we want to compile it as x64 version, ... Microsoft Online Community Support ...
    (microsoft.public.dotnet.general)
  • Re: Linux vs FreeBSD vs SCO
    ... >> often you install an upgrade, and you find it needs something else, ... >> package, from packages otherwise it has to compile Ruby, and some ... in a Maynard Sandstar floppy controller and hung 8" DD floppies ... The official IBM DOS 2.0 manuals and disks are there too. ...
    (comp.unix.sco.misc)
  • Re: Suse 10.3 and DVD::RIP
    ... Gnome began to sort of fork off and became increasingly unfriendly to ... As we are a openSUSE group, that is what I am talking about. ... be problematic to compile is none of my business. ... I have to install 75 MB of stuff to run a 2 ...
    (alt.os.linux.suse)
Loading