From: Frank on
Thanks Marsh for your response. Yes...since each churchboard member will have a responsibilty to nurture the member, so I as secretary want to combine all the data to my database. This is already go live, so I can not change the design of my table or forms any more. the only target now is how can I combine their table with me, since there will be a possibility of duplicate NoteID, how can I combine it by leaving the PK NoteID and only the other field will be appended and the new NoteID wil be regenerated for the imports. There is a filter that only we want to add if Memo filed content is the same, it will not be included in the imports.

Thanks for your help.

Frank



Marshall Barton wrote:

Frank Situmorang wrote:It sounds like the church board members are adding
03-Jan-10

Frank Situmorang wrote:


It sounds like the church board members are adding their
notes to their own copy of the database tables instead of
linking to a single database that resides on one machine.
If that is the problem, you have a lot more issues to deal
with than just merging a few records with the same
autonumber values.

If it is at all feasible, the easiest thing would be to split
the database and have everyone connected to the backend data
tables whenever they use your program.

If they must use the data when not connected, then you could
try changing the NotesID field to a GUID type, but I have
heard reports of other issues doing that. Another approach
would be to derive a different systemID value for each
machine and adding that value in another field in the Notes
table. Then the systemID and NotesID field could be used as
a compound primary key.

--
Marsh
MVP [MS Access]

Previous Posts In This Thread:


Submitted via EggHeadCafe - Software Developer Portal of Choice
RSVP (Rapid Sequential Visual Presentation)
http://www.eggheadcafe.com/tutorials/aspnet/5646196f-b5fa-4d95-b099-c13e46a9ad26/rsvp-rapid-sequential-vi.aspx
From: Marshall Barton on
I seriously doubt that a notes field is an adequate record
key, but it's your program (and your headache). Maybe you
should try using an Unmatched Query as the source for the
append query:

INSERT INTO yourtable ([Date of Note], [Time of Note],
Subject, Note)
SELECT M.[Date of Note], M.[Time of Note], M.Subject, M.Note
FROM membertable As M LEFT JOIN yourtable As T
ON M.Note = T.Note
WHERE T.Note Is Null

Now what are you going to do when some member decides to
edit a previously imported note??
--
Marsh
MVP [MS Access]


Frank Situmorang wrote:
>Thanks Marsh for your response. Yes...since each churchboard member will have a responsibilty to nurture the member, so I as secretary want to combine all the data to my database. This is already go live, so I can not change the design of my table or forms any more. the only target now is how can I combine their table with me, since there will be a possibility of duplicate NoteID, how can I combine it by leaving the PK NoteID and only the other field will be appended and the new NoteID wil be regenerated for the imports. There is a filter that only we want to add if Memo filed content is the same, it will not be included in the imports.
>
>
>Marshall Barton wrote:
>It sounds like the church board members are adding their
>notes to their own copy of the database tables instead of
>linking to a single database that resides on one machine.
>If that is the problem, you have a lot more issues to deal
>with than just merging a few records with the same
>autonumber values.
>
>If it is at all feasible, the easiest thing would be to split
>the database and have everyone connected to the backend data
>tables whenever they use your program.
>
>If they must use the data when not connected, then you could
>try changing the NotesID field to a GUID type, but I have
>heard reports of other issues doing that. Another approach
>would be to derive a different systemID value for each
>machine and adding that value in another field in the Notes
>table. Then the systemID and NotesID field could be used as
>a compound primary key.

 | 
Pages: 1
Prev: Last time it's OK
Next: Thanks for your enlighting