Is there a WYSIWYG program that will allow
us to create a user interface that can be accessed by multiple users
simultaneously to work with the database?
That program is ms-access!! If your access developer is competent, then when
you launch the ms-access interface, you should see NONE of the ms-access
part. And, you don't need to setup security, or even write any code to hide
all of the ms-access interface. I am stating this, since if you are planning
to
deploy this application to several workstations (multi-user) in your
company,
then your developer should be hiding the ms-access interface for you,
and should be creating some nice interface forms and also using
menu bars etc. Doing this will allow you to deploy the application
in what is called runtime mode.
In addition, building a nice interface makes the program MUCH
nicer to use. I talk about a nice interface, and doing this also
allows you to deploy the application as a runtime.
Here is some screen shots, and some ideas as to why building
a custom interface ms-access is most useful.
http://www.members.shaw.ca/AlbertKallal/Articles/UseAbility/UserFriendly.htm
Note that all those nice "menus" for the above where built with NO code, but
just using ms-access.
The reason why I state/ask if your ms-access developer is building a nice
interface, because when it comes time to deploy the application to other
workstations, and those workstations do NOT have ms-access installed, then
you WILL HAVE to had built the user interface. On the other hand, since you
no doubt have a competent ms-access developer, then that person should have
explained all this to you.
I not sure why you would be asking such basic
questions here when you got a developer on board doing this stuff for you. I
am not trying to be a smarty-pants here, but I guess I am concerned that you
have some development process occurring, but then are asking VERY BASIC
questions that any competent developer would know and be able to answer for
you. Remember, like Medicine, or even music, this stuff takes years to
learn.
We can all read and write..but very few can make a living writing. I know
MANY people who can play some music, but few can make a living playing
music. Make no mistake about this, the SAME idea applies to making software!
So, my first thought here is that you should go and talk to your
developer,and ask about these questions. I always used the following rule
for
developing projects:
I am a better hockey coach when Wayne Gretzky is on the team!
The skill level of the developer will make or break the project regardless
Your success of this project is going to be based on the skill level of
your developer.
Hence the #1 consideration is at what level the developer is at. There are
certainly more levels then just "trained" or "not trained". Generally there
are a "lot" of skill levels, but the following breakdown is sufficient. **
Stage 1 Innocent (never heard of the product)
Stage 2 Aware (Has read an article about X)
Stage 3 Apprentice (has attended a three-day seminar)
Stage 4 Practitioner (ready to use X on a real project)
Stage 5 Journeyman (uses X naturally and automatically in his job)
Stage 6 Master (has internalized X, knows when to break the rules)
Stage 7 Expert (writes books, gives lectures, looks for ways to extend x)
One should NEVER attempt a project with a team consisting with Stage 3 or
lower people. This is a sure fire formula for failure. The team can consist
of stage 4's, but they should have at least access to Stage 5, or 6.
Ignore this issue, and your project will fail....
the ability to create executable interfaces for use on a network?
All versions of ms-access since a97 did have what is called a "developers"
edition. This part had to be purchased separately, and you likely don't have
the a97 developers edition (and, it would be VERY hard to find).
So, to answer your question, yes there is a runtime available for ms-access.
Once this runtime is installed, then you can copy/place your ms-access
applications on the workstation, and they will run. So, you do NOT have to
purchase ms-access for each additional PC that you have. This runtime
edition simply is a stripped down version of ms-access that does NOT allow
users to change, or re-design the application (this is what we want
anyway!!). However, in some cases, for reporting, and some query building,
it is in fact beneficial to have the full version of ms-access installed
(especially if your developer is not, or has not been building the nice
interfaces..but has been relying on ms-access here).
So, if your application is designed from day one to hide the ms-access
interface, then the runtime package system will run your software WITH ZERO
work having to be done (and, you do NOT need the developers edition of
ms-access to develop this way. The development process and tools you use is
still 100% plane Jane ms-access). If you spend months and months developing
software, and then all of a sudden decide to deploy as a runtime, then that
person better have been building a custom interface all the way along. If
not, then you will have a WHOLE bunch of work to do!! So, if you plan to use
as runtime from the start, then your developer better be developing and
testing with *intent* to use the runtime system from day one (as mentioned,
they don't need the developers edition..but should be "thinking" of that
fact during the development process).
So, you can do all of this development, and testing with NOT having had to
purchase the developers edition of ms-access, but your developer should be
competent with this issue, and be told that you plan to use runtime here.
So, the additional amount of work to use the runtime can anywhere from zero
work to quite a bit of work.
You can read about the runtime system here:
http://support.microsoft.com/default.aspx?scid=kb;en-us;842004
http://msdn.microsoft.com/library/d.../odc_ac2003_ta/html/odc_acbasicsofruntime.asp
