importing data from another table

[alguzman]

Hi, I have a members database that track all current members, one of the things I track in the members db is education. Our company provide seminars for member and Non-member companies and the boss wants to have the member database and the seminar database separate.

What I want to do is cut down on double entry. How can I automate the procedure of having the seminar database run a append query and export it to my member database in the education table using memberid as the linking fields. So on the seminar database entry form I would have a command button saying export member info now or something to that affect.

 

[jwindon]

How about just creating LINK tables. In one db is the original (doesn't matter which one) and the other is a linked table db. No matter which one you enter into, the info becomes part of each. Thereby two copies of the same info. You can create necessary queries in each to work with the data. You will of course have to add a field to this table that identifys the record as MEMBER or NON-MEMBER.

 

[pcs]

is there some reason why you can't just link the table from the seminar db into the member db? the db's would still be separate, and you would have a more normalized design.

al

oops! jwindon, you're quick on the trigger today !

[This message has been edited by pcs (edited 09-22-2001).]

 

[Pat Hartman]

You have at least one many-to-many relationship. It wasn't clear from your original post whether you keep member information only for companies or for people who work for member or non-member companies. So, I'm going to assume that you said what you ment and you keep the information at only the company level. That gives us a Company table with a member/non-member flag, a Seminar table, and a linking table that links a company with a seminar. This linking table should probably also keep the seminar date since it is probable that a company might require the same seminar more than once.

Although this is not the specific structure your boss requested, it will accomplish the end result and provide a better database for reporting purposes.

 

[alguzman]

Yes our member db is at a company level but also have a linking table that gives info for each employee within the company. The seminar db that I mentioned would have companies which are not members with their employees that they are sending to the seminar who are not members, then there are member companies and employees who attend the seminars.

The member db is just that members only database. I wanted to know when you enter information into the seminar database and have a member company coming for a seminar I can just click a botton with code behind it sending a copy of that member's seminar information to the member data base.

 

[Pat Hartman]

You have made extra work for yourself by keeping separate databases for members and non-members. They should be merged together. All you need is a flag in the company table to indicate that the company is a member company. Then if you want to report on only member data, select only members from the company table.