1 Reply Latest reply on Jul 11, 2011 1:57 PM by philmodjunk

    Setting the foundation



      Setting the foundation


      I am new to FMP and as such I am attempting a rather complicated situation using as much as possible the starter solutions to get me up and running till I can do some more in depth manipulation myself.

      I am keeping track of Student Records, Personnel Records, and Asset Management.

      What I would love to do at this point is take the Lending Library starter solution and instead of trying to import all three of those db's worth of info, just have it reference those DB's to pull the Contact and Asset info from.

      I have figured out how I can reference the external data, and can even perform lookups if necessary. The only thing is I have to manually create a record and populate the ID #'s (Every student, personnel, and asset has a unique # already assigned). From there I can get the fields to lookup. Only problem is I would have to manually do that (or create a script, which I have no clue how to do) and I cant figure a way to pull from two external sources into a single table (i.e. Student and Personnel).

      Is it possible to setup the Lending Library to just automatically create a new Asset everytime a new Asset is created in my asset management (and conversely to delete), is there a way to do the same from both the Student Records and Personnel Records into the Contacts table of the Lending Library? Even if its not automatic I am not opposed to having the records created only when someone or something is checked out, which I can do now, except I cant seem to lookup from two different external sources.

      Am I totally going about this the wrong way?

      Any ideas?

        • 1. Re: Setting the foundation

          It's not impossible to look up data from two different tables if you use an calculation, but I don't think the complexity this produces will make this much of a solution for you.

          Instead of trying to pull data from two different external tables such as student and personnel, you can use import records to merge your records into a single table and use that merged table in both starter solutions. That's much easier to describe in a sentence than to actually carry out as the fields defined in both tables are not the same and after combining the data and using external data source references to refer to the table, you still have to update layouts, scripts, value lists and calculation fields to refer to the correct field in the new merged table.

          You may find it easier to use the starter solutions for example files while you build your own unified solution from the ground up.