preserving reference integrity when moving between bo's

rocketman

This is an "is this possible" type of question.

I have a set of members who never "die" they just "cease to fly" - and that's because there are lots of referenced records attached to the member that I don't want to leave orphaned, such as flight records.

What I'd like to do is create a business object group with two identical files, one for current members and one for lapsed, resigned or dead members.

The question - if I create an identical record in the "old" BO and then delete the record from the "current" BO what do I have to do to ensure the references in the flighlog BO point to the "old" Member BO rather than the original "current" BO

kklosson

I would think that it would be far better to simply set a status for your members; Active, Resigned, Died in Fireball Crash, etc. Then set your queries to view the categories you want to view, or restrict the view for certain access levels. I think the path you described above is more painful than a flat spin.

rocketman

You speak just like a pilot kklossen.

That's what I have at the moment. The problem was(is) that certainly for the next few months we are going to have to live with our old access based Financial system and will be linked table through to the Aware DB. I was just trying to make life simple for the guy who manages the Access database

I should add I know nothing about Access except that I don't particularly like it

tford

Rocketman,

What's the relationship between the flight records and the pilot -- Peer or Owned By?

Tom

kklosson

http://books.google.com/books?id=ZN62AOin1LIC&pg=PA157&lpg=PA157&dq=klosson+perfect+storm&source=bl&ots=uk82XKM96S&sig=dP6YGdeAWIDveB8gUTuwx2_IluI&hl=en&ei=JaidSY7TF5jAtgfz8JDiBA&sa=X&oi=book_result&resnum=2&ct=result

rocketman

Hi Tom,

The flight record has peer links to the members file (to provide an online log book) and an Aircraft file to provide legally required flying hours per aircraft

tford

Hi Rocketman,

Try something like this:

1) Create a process called MoveFlights.
a) Process Inputs: Member, FormerMember, Flight
b) 2 Rules:

INSERT Flight IN FormerMember.Flights
REMOVE Flight FROM Member.Flights

2) Create a process called MakeFormerMember
a) Process Input: Member
b) 3 Rules:

CREATE FormerMember WITH FormerMember.Name=Member.Name,FormerMember.Flights=Member.Flights
FIND Flight WHERE Flight IN Member.Flights
MoveFlights (this called the process from #1 above)

MakeFormerMember could be invoked from a Member form. It will create an identical record in FormerMember, then add the Flights to the FormerMember instance and remove the Flights from the Member instance.

Hope this helps.

Tom

rocketman

Thanks Tom .... Nearly midnight here in UK - will try this tomorrow