in message
(e-mail address removed)...
Hi,
I have created, tested, and yes even sold an access application. However
the
access application is not in any state to distribute professionally (they
would need access on their desktop and they can see my tables and forms
and
code etc)
The building of a nice interface, hiding the ms-access interface, and making
some nice menu bars etc is all possible in ms-access. No special or
additional tools are need. I would think that if you reached the point of
actual distributing, or selling an application that the spit and polish part
of hiding the ms-access part would have been done long ago. So, yes, you can
certainly hide the ms-access interface, and you should. In addition, you
likely have a split database (else, now can you support updates and bug
fixes). Further, since your database is split, then you likely have added
code to re-link tables etc....right? And, like you always distribute a
mde...right?
If you as a general rule can't say yes to any of the above questions, then
you are not ready yet to deploy your application.
Here is some screen shots of some menus, and why I use them in ms-access:
http://www.attcanada.net/~kallal.msn/Articles/UseAbility/UserFriendly.htm
And, for reports..you provide a nice interface also...right? Here is some
screen shots of reports screens:
http://www.attcanada.net/~kallal.msn/ridesrpt/ridesrpt.html
And, if you want a sample application that has the ms-access interface
hidden, you can grab the 3rd file here:
http://www.attcanada.net/~kallal.msn/msaccess/DownLoad.htm
So, take a look at the above to see the options (they are in tools->startup)
that i used to make the above.
Anyone can tell me if it is possible to make it so it downloads off the
net,
self extracts, hides source from users, etc.?
The hiding of souce, and all the menus is something you can, and should have
done already. To remove the source code, you use a mde. As mentioned, if you
have not been using a mde now, and not a split database, and not have hidden
the ms-access interface already..then you are not ready for prime time. All
of these things like making your own menus etc is required for the runtime
system. So, yes, there is a runtime and packaging system available for
ms-access, but it don't make your menus for you! So, hiding the interface
etc does not need a runtime, or special install system, but requites you to
do some more work!
So, before purchasing or using the runtime system...you need to do the above
things.
So, you can purchase the developers extensions to ms-access. The resulting
file is a end user installable application. The user does NOT have to have
ms-access on the target pc. This packaging wizard actually creates a
standard windows install package for you. Make do doubt about it, while the
end user does not have to have ms-access, or even know your product is
written in ms-access, you are in fact installing a version of ms-access on
the target computer (just no design tools etc are able to be used..and you
have to build your OWN interface) As mentioned, you likey would have hidden
the interface stuff a long time ago anyway...right? If you not done this
yet..you not ready for the runtime deployment system.
The install library is about in the 30 meg range + your application. So, its
i quite large, and not really usable or deploying over dial up lines.
