Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

"Integrate Modules" ???

Status
Not open for further replies.

dbswifelb

Technical User
Sep 18, 2005
3
0
0
US
If a tech is suggesting that we integrate some of our modules what would the benefit be?
We are having an issue with translation and we just don't understand what our tech means.
Can someone please help?
 
Yes you are right you are having an "issue with translation" and on more than one level I'd suggest.

What are your issues that this tech thinks will be addressed by "translation" ?


Are your modules that the tech is refering to :-
"Class Modules" or "Form Modules" or standard "Modules" ?

and what version of Access are you running because a Class module in A97 is completely different to a Class Module in A2k and beyond.


Do you 'trust' this tech or is he an outsider looking to make work ?





G LS
spsinkNOJUNK@yahoo.co.uk
Remove the NOJUNK to use.
 
TheTech said:
integrate some of our modules

Are yoy talking about integrating program modules or integrating systems?

Advantages os integrating systems is to consolidate your data...

For example, suppose you have several "subsystems"...
- order entry system in customer service
- shipping system in shipping / receiving
- purchasing has a contact and supplier database
- contact database in sales
There is a lot of duplicate data here. Suppose the company moves, or there is a new sales person, etc. A change is made in one subsystem but not in the others.

By consolidating the customer / supplier / contact info into one database, there is one database with all your contacts, customers, suppliers. All departments see the updated info. Less duplication of effort, less maintenance, more accuracy.

The trick here though is to ensure the database meets everyone's needs. If a system does not meet the needs of those using it, then there is a tendency to ... create another subsystem.


If you are talking about integrating modules, then it can be much the same thing. An old problem used to be that you needed several supporting files in addition to the application. For example, MDAC and DCOM.

However, these days, applications are much better at being backward compatable, and there is much more compliance between programs. Only problem I run into these days is compatability problems with different versions of Java.

Richard

This
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top