Module Import or Export (1 Viewer)

access2010

Registered User.
Local time
Today, 12:09
Joined
Dec 26, 2009
Messages
1,088
We are going to hire a person to update one of our MsAccess forms.

Should we have the programmer update the form in a new Module and this way we could Import the New form and Module into our existing database and have it work?

Comments are appreciated.
Nicole
 
you can use the access menu:
external data
datasource
from Access
import
select the db to import from
select the modules & forms to import
 
That is actually a very difficult question to answer as it depends on a lot of factors. Also, technically, when you build a form, you build the Class Module for that form at the same time. To Access, they are in one sense inseparable. If the form has to deal with data in the main DB, your programmer will have to have a working copy of the data tables somewhere as a test-bed. Here's a link or two:




These three links will lead to a discussion of how you develop while users have live activities going on. Links withing the links will give you a lot of reading matter, but it may help you orient yourself to a viable setup.
 
you can use the access menu:
external data
datasource
from Access
import
select the db to import from
select the modules & forms to import
Thank you Ranman246 for your comments.
Previously, we would import the modified form and then the code on the form as separate items. But this process nearly almost always left out some of the code.
PLEASE confirm that that this is the way we should proceed?
We will now try for the FIRST TIME to have the programmer put all of their code into a separate Moduale and then we would A=Import the new form and B=Import the Modual with all the code.
I appreciate your comments Nicole
 
That is actually a very difficult question to answer as it depends on a lot of factors. Also, technically, when you build a form, you build the Class Module for that form at the same time. To Access, they are in one sense inseparable. If the form has to deal with data in the main DB, your programmer will have to have a working copy of the data tables somewhere as a test-bed. Here's a link or two:




These three links will lead to a discussion of how you develop while users have live activities going on. Links withing the links will give you a lot of reading matter, but it may help you orient yourself to a viable setup.
Thank you The Doc Man, Zayde for your comments which we ALWAYS appreciate.
Nicole
 
Previously, we would import the modified form and then the code on the form as separate items. But this process nearly almost always left out some of the code.

IF the code is part of the form's Class Module (rather than in a general module) you should be able to do what RanMan256 described. IF, on the other hand, the code is developed in a separate module, you were not just developing a form. Code in a separate module can't directly be used for any event code. It can be CALLED by VBA from an event routine, but the event routine link from a form cannot be to a general module unless you built a public function - which CAN be event-triggered in some cases.
 
Should we have the programmer update the form in a new Module and this way we could Import the New form and Module into our existing database and have it work?
If was your programmer, I would ask for the whole system, your FE and your BE. I would then make the requested changes to the FE. Then I would return the FE to you for testing, with an incremented version number, and a description of the changes made under that version number. If you are happy with the work, then you would simply replace the entire FE on any computers that require the change.
 
I wish to thank you all for your suggestions and everything was imported into our existing database without a problem.

Nicole
 
Should we have the programmer update the form in a new Module and this way we could Import the New form and Module into our existing database and have it work?
No. The first task is to split the application into a FE and a BE. The BE (back end) holds only data tables. The FE (front end) hold all the forms/reports/macros/code and links to the tables in the BE.

Once the application has been properly split, the second task is to create a distribution method so that each user has his own personal copy of the FE that links to the BE.

If the person you hire does not understand how to do either of these two things, do NOT hire him. find someone else.

Once the app in its current state is properly set up, then your new programmer can begin to work on changes. You need a method of sharing the testing version so you can test his changes and approve them. Then they can be distributed to the rest of the team for use with production data. This allows you to see frequent, small, upgrades as the programmer works through your task list.
 

Users who are viewing this thread

Back
Top Bottom