GetIDFor
Available in The SalesLogix Client, the Support Client
Function Gets the new ID for a given table.
If you are creating a new record for a table and need the ID before posting the record to
the database, call this function to get a unique key to assign to your record. An example
of a time when you might need to know the ID is when you are creating one or more
records in a related table and need to populate the foreign key in that record and post
the records together.
Object Application.BasicFunctions.GetIDFor
Syntax GetIDFor (TableName)
Parameters TableName - the name of the table you are creating a record for.
Returns New ID or Primary Key for a new record in the table

1. Enable the AUTOINCREMENT feature for the ACCOUNT.ACCOUNTID, ADDRESS.ADDRESSID, CONTACT.CONTACTID etc fields. To do this, go to the SECTABLEDEFS table, find these fields and set the AUTOINCREMENT field to 'T'. What this means is that you won't need to create IDs for these fields, they will be automatically generated for you by simply omitting them from your import.
   
   
2. Build a DTS package that uses the data from the user tables (USERINFO, USERPROFILE, ADDRESS, etc) as the source and then just inserts the user data to the following tables (via the SLX Provider - ie: use the SLX Provider as your connection type for your target in the DTS package)
   
   To create the account you must insert to these tables
   
   • ACCOUNT (Set ACCOUNTMANAGERID='ADMIN', SECCODEID='SYST00000001', CREATE/MODIFYUSER='ADMIN', etc)
     
   • ACCOUNTSUMMARY
     
   • ADDRESS - each record needs to get it's own row to link to
   
   
   To create the contact record you must insert to these tables
   
   • CONTACT
     
   • ADDRESS - each record needs to get it's own row to link to (separate record than the account record)
   
   
   
3. As far as knowing which fields you need to populate, I would just suggest to fire up the client, create a sample record exactly as you want it to end up then go and look at the tables I mention above to see what the data looks like and you can mimic that in your import.
   
   
4. You could even schedule the DTS package to keep the contacts/accounts in sync with the user data if you wanted (as long as you built in the ability to do updates in the DTS package so you're not creating new record each time)

'HowTo - Create a Transform for using SLX_DBIDS

If you are on a recent version of SLX, you can use the SLX_DBIDS 'stored procedure' to populate the IDs.

Create a data driven query task that grabs all of the Access data that you want to map and create a transformation to all of the fields you want to populate (excluding the IDs).

Then add another transformation - this time ActiveX scipt - that maps to the ID field.  Here is some sample script to generate IDs:

'**********************************************************************
'  Visual Basic Transformation Script
'************************************************************************

'  Copy each source column to the destination column 
Function Main()
  Dim strConn
  Dim objConn
  Dim objCmd
  Dim rs

  strConn = "Provider=SLXOLEDB.1assword=""""ersist Security Info=True;User ID=admin;Initial Catalog=xxxxxx;Data Source=xxxxx;Extended Properties=""PORT=1706;LOG=ON"""

  Set objConn=CreateObject("ADODB.Connection")
  objConn.open strConn

  Set objCmd=CreateObject("ADODB.Command")
  objCmd.ActiveConnection = objConn

  objCmd.CommandText = "slx_dbids('" & "tablename" & "', 1)"
  Set rs = objCmd.Execute()
  DTSDestination("ID Field name") = rs.fields(0).value
  Main = DTSTransformStat_OK
End Function