Importing and record IDs

tford

PM Question from george.greiner re:

george.greiner

So for instance I need to query data from a disk we get from a vendor into the new tables I made IN AwareIM; can I import those files into the table? If so what do I do about the ID field that is automatically created by AwareIM as I already will have an ID when importing certain data---do I have to create the record first as opposed to taking the text file we get from our client and importing that into the tables if the order is too tedious for them to order one at a time through the webapp order process I made or when I query data from another application into AwareIM tables with one to many relationships?

I guess the issue I am having is that I have only really ever worked with Access and SQL and this is a bit more abstract with the way references and other functions work (I still do not understand what those are keyed by at this point) since I never actually make a key.

What is the Basversion field for?

tford

Is this a one time import or an periodic import/update/add instance into AwareIM?

george.greiner

tford wrote
Is this a one time import or an periodic import/update/add instance into AwareIM?

Depends. For instance I will have to do one import a month into various tables. Other instances the table will update from another application for each record when that function is completed etc etc.

tford

Thanks George. I have to leave right now, but will post a summary later tonight.

george.greiner

Let me tell you exactly what happens instead of being vague. BO 1 is a one to one relationship that is created when an order is created (this needs to be created either by:

order created on the ordering form
by an import of a text file (this normally happens from 1 vendor each week of 100 files).

Then for each file a search is done in another application and it can include up to lets say a max of 500 separate records using a 1 to many relationship and this will be dumped into a table that holds these records and needs to be output for each record (eventually we will make this function part of the web app if possible). There are several other of these instances in which a search is done automatically and then dumped into its corresponding table using a caseID as the one to many relationship and then its own indexed key (key +1).