July 1, 200322 yr Hi Joe, Take a look at The Gateway by Giuseppe Pupita available at http://fmfiles.com/ 2nd file I believe listed. HTH Lee
July 1, 200322 yr You can use a global on the left side of a relationship. For a start, create a "Constant" field, a number calc that = 1 in all your files. Then make a relationship based on that, that gives you all records in the related file. Make sure the relationship does NOT have "when deleting, also delete related" checked! I'm not sure how you want to relate the user ID to the other files, but that would require the user ID "belong" to the related records. A global on that side of the relationship would be meaningless. If more than one user is going to belong to a related record, you could use a multi-line key in the related file, where each user's ID & paragraph symbol is added to a field via script.
July 5, 200322 yr Author Thanks for the replies Lee and Tom. As for that Gateway solution, it's way beyond me. I have no idea whats going with that. Tom, I'm going to give your "Constant" field a try. I'm not sure why I wanted to have the user (by number) related to the others files. I just wanted a way to get data from those other files through the front end database and couldn't think of how to do it. Hopefully I'll be able to do what I need using your idea. Joe
July 16, 200322 yr Joe -- I have done what you are talking about and created front end databases that are really just layouts with related portals into the databases that hold the information. I have also created front-end databases that are truly "view-only" in that the data is entered into one database and then exported out to a "holding database". Each time the front end is opened, it imports the records from the "holding" database and displays it for the end user. I use this in a sort of Kiosk display that shows our associates key information from a lot of different files. If you need more information, my e-mail is [email protected] Scott
Create an account or sign in to comment