Access application Deployment

[coyote]

Hi guys
I have designed an application in access 2003 and recently I upgraded to access 2007. I have down loaded the free packaging wizard and access 2007 runtime.
My application is split in to two,the front end and the back end.
I want to deploy this application to users who do not have access 2007 in their machine and am using the packaging wizard
My questions are
1. Will the back end be re connected with the front end (I have a reconnection function which runs at start up using the auto-exec macro also I have added the back end as an additional file)
2. When I want to upgrade the front end how will I do it without affecting the back end
3.Anybody with an idea how to get hair salon related icons will help me a lot(I know guys this is not related but the application is for salon management)
4.Also how to get a calendar like the one for outlook to be used in an access application(same as three)

Your help is greatly appreciated
Cheers

 

[CEH]

Well, I'll only give you a little info on one part of your post. When you distribute your application you only want to package the Frontend. Your giving it to users that "don't have Access" So I assume some of them do and are already using your split application. And if your code to connect to the backend works, then their set. You do NOT want them to be loading another back-end! Depending on how you answered the errors that would come up, it would either overwrite your existing back-end (AND ALL YOUR DATA) or create many different back-ends.
You can update or change your frontend forms, queries, reports... whatever, without disturbing anything on the backend. The exception here would be if you are adding fields or changing them in some way. You would then need to alter your tables in the backend.

 

[MagicMan]

CEH...right on. Coyote, you may have to create some procedures to convert the 2003 database if you have changed any defiitions. I have a BE version number in the Settings table. When the version of the backend doesn't match the front end, I display the database conversion form which covers all upgrades (even skipping 3,4,5 etc versions) by executing the appropriate procedures. The form prompts the user to do a full backup before continuing (allowing the user to cancel and come back after the backup), identifies the user's current version, the new version, and displays the version info notes. Hope this helps.
Bob

 

[coyote]

Thanks Magicman
My problem is when packaging the application the wizard just gives me the option to package one part it can be either the front end or the backend not both
Will I be able to reconnect the DBs if I add the backend as an added file
Also I dont know how to use the system table and form you are saying
can I have a sample

On another note something funny here
when I open the application using access 2007 without converting some forms are opening as dots which is so weird what can be wrong because all the references are OK
Cheers

 

[MagicMan]

The settings table is a table I create. This table contains application settings, some pre-loaded and some prompted at first use. The pre-loaded include version numbers of the distributed package, version of Access, version of SQL Server. Prompted data is Company Name, Address, Hardware (assisted by vba code), Print Defaults, Security Definitions, Currency Definitions, User specific standards based on the local governement rules, etc,etc. The settings for my applications usually involve multiple popup sub forms to aquire all the parameters required to establish the operating environment for that specific trade, in that specific Country/province/state. (My forms are dynamic based on these parameters...Eg: FormA used by Joe looks nothing like FormA used by Henry, even though it is the same form with the same underlying code. Joe has 15 fields, Henry 65...both perform the same function.
When the system date changes, the first login triggers an application that confirms the BE version has not changed, the FE has not changed, the Application has not changed. If a change is detected, the appropriate action occurs...Access has been upgraded to 2007, the application provides a pop up which details the steps to follow to ensure the application runs smoothly. If the application (Forms, Query's, Project) has changed, the application is locked to all but the adminstrator, who should have confirmed the application patch. If it is not a valid patch, then the modification information by user, ip address, time are presented to the administator to allow him to identifiy and or block the hacker from future attempts. There is a lot of code behind all of these functions, and most of it is application specific, but I hope you get the drift.
I only redistribute a FE. The BE is distributed at first time installation. After the first install, only FE patches, or new releases are distributed. If a database must be converted or changed, a conversion procedure is delivered in the front end, and triggers at first login after the patch/new version is applied. The database backup, make table, add field(s) procedures are run and upon successful completion, self delete.

Your Calendar question ... see this link http://www.rogersaccesslibrary.com/forum/forum_posts.asp?TID=165

Hair Salon Icon ...Cutter... http://www.iconarchive.com/category/people/more-people-icons-by-brown.html