Re: MDE and runtime

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: How to pass information, classes between forms in Windows Application mode [ FINALLY!]
    ... In a WinForms app generated by Visual Studio, ... A constructor in my "book" is the stuff that appears in public ... wouldn't compile as the appropriate constructor signature hasn't been ... declarations, it will compile. ...
    (microsoft.public.dotnet.languages.csharp)
  • Re: MSAccess to Web App
    ... I agree that an A97 app is long in the tooth nowadays, ... PC- based application, that is, support of as many different PC ... This is something that *you* care about but your clients don't. ... Sure, they know they are paying for only a year, but they don't like ...
    (comp.databases.ms-access)
  • Re: [PHP] Working as a PHP/database developer..
    ... There are no fixed fees. ... > PROFIT, rather than braking even all the time ... > b) enforced by you when not observed by clients ... > You can always compile your scripts, ...
    (php.general)
  • Re: RemoteApp Dialogs Disappear
    ... I tested it with WordPad and it happens there as well. ... only with message boxes that generate a beep. ... We are publishing our app through RemoteApp (Terminal Services ... this behavior varies between clients. ...
    (microsoft.public.windows.terminal_services)
  • RE: Windows XP and VFP 8.0
    ... This error message is not a VFP error. ... Have you contacted the developer to ask him what might prompt this error? ... >The app is served in a shared folver by a Win98 pc. ... Clients are WinXP, ...
    (microsoft.public.fox.helpwanted)