Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

This topic is 8542 days old. Please don't post here. Open a new topic instead.

Recommended Posts

Posted

G'day, Some assistance please. This subject has been covered a number of times in this forum. (Went thru 10 pages and found at least two hits a page) However, despite printing out a number of relevant posts, I am unable to apply the information presented.

I have a database "Flight Data" which records ten or so parameters. These are identified by a auto entry sequence field (no modification allowed). I want to transfer this auto sequence number onto a minimum of three and upto five seperate File layouts ("Landings", "Route", "Instrument Flight","Fuel","Oil").A single flight may involve mutiple records in "Landings" (due to different Locations) and "Fuel".

Any ideas? Specifically I refer to a topic initiated by Oases and answered by yafreax & Chuck. In this topic Chuck & yafreax discuss utilising a "relationship pipe". Is it possible to apply this to the scenario I have descibed? If so, could someone provide guidance?

Thanx. Sorry about getting a touch of the Southerlies in this post.

Posted

I'm a little confused by your terminology. "File layouts" is alien to me. Are you trying to "transfer" your unique number to different layouts (I think not, just place the field on the layouts) or to different related files? Are "Landings", "Route", "Instrument Flight","Fuel", and "Oil" separate related files?

A little more structural information will be useful in helping you with your question.

-bd

Posted

quote:

Originally posted by Greg Smith:

G'day, Some assistance please. This subject has been covered a number of times in this forum. (Went thru 10 pages and found at least two hits a page) However, despite printing out a number of relevant posts, I am unable to apply the information presented.

I have a database "Flight Data" which records ten or so parameters. These are identified by a auto entry sequence field (no modification allowed). I want to transfer this auto sequence number onto a minimum of three and upto five seperate File layouts ("Landings", "Route", "Instrument Flight","Fuel","Oil").A single flight may involve mutiple records in "Landings" (due to different Locations) and "Fuel".

Any ideas? Specifically I refer to a topic initiated by Oases and answered by yafreax & Chuck. In this topic Chuck & yafreax discuss utilising a "relationship pipe". Is it possible to apply this to the scenario I have descibed? If so, could someone provide guidance?

Thanx. Sorry about getting a touch of the Southerlies in this post.

I assume that you are refering to seperate database files, and not simply seperate layouts within the same file?

If you are transfering data between two different files, then there are a whole host of ways to accomplish this. One way is to store your ID in a global field, create your new record and simply set the new ID to the value stored in the global. Another way is to setup relationships that allow the creation of related records, then simply use a set field (any field to any value) through that relationship, and the IDs will be correctly transfered.

Speaking of IDs - I HIGHLY recommend that you cease the use of a simple sequential serial number (modifiable or not) as you ID. They are simply to easy to get screwed up, or duplicated, or copied, or whatever. I use an auto-entered value : Right( "00000" & Status(CurrentRecordID), 6 ) & "-" & Right( "00000" & Status(CurrentTime), 6 ) & "-" & Right( "00000" & Status(CurrentDate), 6 ), which is virtually unduplicatable, very unique and thus far unbroken after many years of use in very complex solutions.

Make sure to make your IDs text fields, even if they contain only numbers. There is nothing that you cannot do in a text field, and there is a ton of stuff that you cannot do with a number field.

Also make sure that the user does not ever have access to this number.

You can continue to use your serial number as a user identifiable number that they see throughout the solution, but do not use it for actual record identification.

Posted

Morning, Sorry for my poor use of terminology. Attempt Two: "Flight Data", "Landings", "Route", "Fuel", "Oil" & "Instrument" are separate files. I want to link them using the same identification field called "Flight ID" which is generated in "Flight Data". One solution is to copy and paste from the origin file "Flight Data". I do not think this is a robust solution. Thanx Captain Kurt for the tips on ID files - I was not aware of the implications and will change my ID fields.

This topic is 8542 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.