Walt Smith said:
Need to develop an "special" accounting database system, and have the
following questions:
1) Is there a way to completely "hide" the forms, queries, and tables from
the users. Security is upmost important with this project?
Yes, you can, and should as a course of development hide the ms-access
interface. You don't need, or have to bother with security to accomplish
this. Security is used for what forms, and what reports and what information
a user should/can allowed to be seen. However, you can have security, and
still not hide the ms-access interface. So, security, and hiding the
ms-access interface is two separate issues. However, the answer is yes, you
can completely hide the ms-access interface, and you don't need security to
do this. You can download a a97 example of this at:
http://www.attcanada.net/~kallal.msn/msaccess/DownLoad.htm
Grab the 3rd value. After you run and play with it for a awhile, you can
exit, and then launch the application again, but just hold down the shift
key while it loads, and you will get into the design/ms-access window. All
of the settings required to "hide" the ms-access interface completely are
available in the tools->Start-up.
2) Can you compile the program in such that the user is not aware that this
an Access program?
Well, if you do option #1, then you kind of do accomplish this goal. I mean,
I am sure you do things like build your own custom menu bars etc in
ms-access. So, if you are tying to "hide" the ms-access interface, then I
sure you a long time ago built your own menu bars, and tools bars. So, you
don't have to compile the program, nor can you to hide the ms-access
interface. However, you as developer will usually distribute a mde to hide
your source code, and also take the ability to change/design forms from your
users. You can also hide the ms-access splash screen at start-up. In
addition, after all the above is said and done, you can even purchase the
developer edition of ms-access that allows you to create a run-time install.
This install allows you to install the software on pc's that don't have
ms-access. (so, the target user does not have to purchase/install ms-access,
as the runtime system will do this install for you).
3) Is it easy to convert the forms, queries, and database from access to MS
SQL access? Or if you plan to use SQL, develop system from the start with
SQL?
Well, I guess the above depends on how much sql server experience you have.
If you have lots, and are experienced, then not much work needs to be done.
However, if from day one you plan to use sql server with ms-access, then I
strongly consider using a adp project from day one. It would not make sense
to develop the application with JET,and then convert to sql server if that
is the final goal.
Anyone suggest good "development" documenattion to tackle this procect in
the speediest matter!
There is no shortcuts. To develop quality applications in ms-access you
need:
Good table design and normalizing skills. If you don't have these skills,
then you need to spend some time on this issue.
Good VB skills. The programming language in ms-access is VB. So, any good
programming and coding skills you have will go a long way.
SQL. Good sql skills really again can help you develop a good application.
Good ms-access skills. You need to learn the forms model, and other parts of
the ms-access object model. You should also spend some time learning how to
create menu bars, and tool bars in ms-access. Learning security would also
help too if you need to have users with different levels access to
information.
To get good at all of the above skills can take some years of your time. I
would consider some books in each of the above areas. I would fire up google
newsgroup search on this newsgroup, and do a search on books.
