Hi, Chris.
[color=blue]
> For clients with no Access, can I still give them an Access
> database with the Access forms as the gui?[/color]
Not quite. One can distribute the *.MDB file to users who don't have Access
installed on their computers, but these users won't be able to use the file
unless they extract the data from it by using another application, or they
know how to write a script to do so (i.e., a non-Access GUI or "front end").
In other words, "Access not installed" means none of the great application
development tools, Access objects, or GUI are available.
However, one can purchase the Access Developer Extensions with Visual Studio
Tools For Microsoft Office 2003 (or the Microsoft Office Developer's Edition
(ODE) for earlier versions of Access, but those are harder to find) for the
license to distribute an unlimited number of copies of the runtime version
of Access 2003 (or the same version of Access as the ODE version). The
runtime version of Access can be installed on the user's computer at no
additional cost to them, and the user will be able to be able to edit the
data and use the forms, queries, reports, macros, et cetera, that the
developer has created, but won't be able to change the designs of these
objects.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
"NewToPython" <nospam@nospam.com> wrote in message
news:8l8ul0l051k54550s31g06nrj2hbcfmtq4@4ax.com...[color=blue]
> On 2 Oct 2004 09:53:18 -0500,
d.REMOVEschofield@blueyonder.co.uk
> (David Schofield) wrote:
>[color=green]
> >On Sat, 02 Oct 2004 04:04:45 GMT, NewToPython <nospam@nospam.com>
> >wrote:
> >[color=darkred]
> >>I am going to build an application for a small business that may be
> >>able to be used at other businesses. I am trying to decide which
> >>route to go in building the application - which will require
> >>persistent data storage (a database). I am between VBA in an Access
> >>database and VB/VC/or Java with a MySQL database. Obviously with the
> >>second option I would have to install a DBMS on the target PC, create
> >>the database, then deploy the app (configure, etc).
> >>
> >>With regards to VBA in an Access database, what does it take to deploy
> >>my app/database to a PC that does not have MS Access (maybe doesn't
> >>even have MS Office at all). Probably just targeting WinXP. Do I
> >>need to distribute VB run time modules? Database related files?
> >>Anything else?
> >>
> >>It has been a few years since I made an app within Access, is there a
> >>FAQ out there to answer simple questions like:
> >> How do I make it so that a user cannot get out of y menu system?
> >> How do I make it so that my menu automatically comes up when the
> >>database/application is started?
> >>
> >>Thanks for any suggestions while I determine the path to travel in
> >>what will hopefully be an exciting journey.
> >>
> >> - Chris[/color]
> >Hi
> >Just a couple of points from me and some of my prejudices
> >.
> >By the "Access" route you presumably mean using Access for the forms
> >etc. The alternative is VB, C (don't do it!) or Java...
> >Raising MySQL is a different issue, as either method can be used with
> >any of the different back ends (Jet, MySQL, SQL server, Oracle, db2,
> >Postgres).
> >Access front end by far the quickest. Even if you follow one of the
> >other paths you can develop support/debug/reporting parts in Access
> >(output in pdf not snp) and keep this to yourself.
> >Java by far the hardest - avoid EJBs!
> >Access most trouble to deploy because run-time systems problematic
> >under later versions of windows. Most users will have office, in
> >different versions, including some with Access already, and new
> >versions will keep coming out. (Good for developers with robust
> >support contracts, bad for clients although the original cost will
> >have been less)
> >Have you thought of developing it as a web/intranet app.?
> >David[/color]
>
> I thought of doing it as a web app (the future of what I have planned
> includes web access to the data), but my target is a single,
> stand-alone pc used by a person who is not that PC literate. The
> Access forms/db all tied in one seems like it would be the least
> maintenance from the user's perspective (I would throw in a backup
> option of some sort). The businesses I am targeting will not have
> much more than a PC and the one I am starting with only has Office XP
> Standard - no Access.
>
> Thanks for the tips of staying away from Java - I want to learn Java
> and thought this might me a good project to learn that with, but time
> is of the essence now, so I was thinking of at least starting with
> Access forms on an Access database. I can always rebuild with VB
> talking to whatever database (that makes the product more flexible).
>
> I am looking to keep the client's cost down when receiving the product
> (allows more profit for me, keeps me competitive in pricing).
> Besides, I am targeting a niche market that does not have a lot of
> money for initial investment and ongoing support. That is why I am
> looking at open source / freeware technologies...
>
> I currently have Visual Studio 97 Pro and Access 2000. I figured that
> in the worst case, I could do it in Access 2000. Later I could use VB
> from Studio 97 attaching to a DBMS. From the profits of my first
> sales, I would then upgrade the Studio or whatever I end up using for
> the GUI.
>
> Thoughts? For clients with no Access, can I still give them an Access
> database with the Access forms as the gui?
>
> - Chris
>
> - Vacation Club Boy[/color]
