Maracay said:
Thanks, that is what I needed. I have another question; in this scenario
where the database will be in the server and the application in the
workstations, thinking in data traffic what is the best choice to filter
data
for the reports; to use the WhereCondition just before opening the reports
or
place a condition in the Criteria in the query.
Having to modify the queries is too much work. I suggest using the "where"
clause, and it will only drag down across the network the records it needs
if there is a index that can be used on the criteria passed......
You can also read my article on splitting here, as I also mention some
details such as what happens when you need to add a new table etc to your
applications.
http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
And, for hiding the interface, you can't create a .exe, but you can and
should create a mde...
here is a repost of mine on tihs:
------------
You most certainly can, and should hide all of the ms-access interface. The
options to complete hide and keep people out of the ms-access interface can
easily be done using the tools->start-up options. Using those options allows
you to complete hide the ms-access interface (tool bars, database window
etc).
Also, using these options means you do not have to bother setting up
security.
Try downloading and running the 3rd example at my following web site that
shows a hidden ms-access interface, and NO CODE is required to do
this....but just some settings in the start-up.
Check out:
http://www.members.shaw.ca/AlbertKallal/msaccess/DownLoad.htm
After you try the application, you can exit, and then re-load the
application, but hold down the shift key to by-pass the start-up options. If
want, you can even disable the shift key by pass. I have a sample mdb file
that will let you "set" the shift key bypass on any application you want.
You can get this at:
http://www.members.shaw.ca/AlbertKallal/msaccess/msaccess.html
Of course, during development, you will hold down the shift key so your
startup settings don't run. You then develop for awhile, and then to test in
"user" mode, you exit..and then re-enter the application without the shift
key bypassed. You will likely do this dance all day long as you run/test as
user mode, and then flip back in to developer mode (shift key used..so you
don't get the main custom menu). So, you can't develop, or really modify
things when you run your application with the startup settings...so you must
shift-by-pass them when you want to work.
And, in fact, I use alt-f4 to exit the application...the mdb file should
still be highlighted in the windows explore..so, then you hit enter key
(and, hold down shift key if you need be). This key stroke sequence and
exiting and re-entering the application will occur CONSTANTLY all day long
when you are developing.
When you finally have things just right...you create the mde
you plan to distribute.
