How do you distribute backend?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Larry Hodges - 26 Apr 2006 23:13 GMT

Hi again everybody,

Running A2002 Dev.

In the A97 days, when creating a Package, you could include the Backend, and
stipulate that it should not be uninstalled, or overwritten upon
re-installation of the Package. Of course, from A2000, we've lost that
ability.

So how do you distribute you Backend?

And is A2003 with the Visual Studio Tools any better at this?

Thanks,
-Larry
Maximize Software, Inc.

Reply to this Message

Alex Dybenko - 27 Apr 2006 09:34 GMT

Hi Larry,
I would better do not include BE into setup at all, as some user can
accidentally overwrite it, even there is an option in setup.

Perhaps you can consider using more sophisticated installation software,
where you can check that BE exists, and several times prompt user if he
really like to overwrite it.

Signature

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

> Hi again everybody,
>
[quoted text clipped - 12 lines]
> -Larry
> Maximize Software, Inc.

Reply to this Message

Rick Brandt - 28 Apr 2006 19:03 GMT

> Hi again everybody,
>
[quoted text clipped - 12 lines]
> -Larry
> Maximize Software, Inc.

My install includes an empty back end fiel with "_Blank" inserted at the end
of the name. My front end has "Run ONce" code that first looks for the
proper back end file name and if it doesn't find it renames the "Blank" one
to the correct name and then refreshes the links to that file.

With this strategy an install or update never over-writes an existing back
end file because it simply doesn't have a file with the same name, but when
the install is a fresh one then a back end file is still present to use
after startup.

Signature

Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com

Reply to this Message