Want to get rid of Google Ads, click here.
+ Reply to Thread
Results 1 to 2 of 2

Thread: SQL Mappings

  1. #1
    Senior Member
    Join Date
    Jun 2002
    Location
    Texas
    Posts
    374

    Default SQL Mappings

    I've been having a little bind the past couple of days.

    In the SQL utilities menu, select Modify Existing SQL Mapping, I am working on the problem table.

    I have created a number field called hours.worked and I have specified its SQL name as hours_worked; the SQL type is float; the SQL Table is m2 (I have also tried m1 and m3); and the SQL RC is false.

    The trouble I am having is that when I open the tables in SQL, the field has not been exported. When trying m1 or m3, it still does not go through. Strangely enough I have also created hours.worked in the incidents table, and it exports just fine.

    My question is that in the problem table, it is at level 3, index 3. If there is another fieldname with the same level and index, is that what is causing the problem? How can I remedy it? I've tried regen-ing the dbdict but that didn't change the level or index.

  2. #2
    Senior Member
    Join Date
    Jun 2002
    Location
    Texas
    Posts
    374

    Default

    Well I have diagnosed the problem and it was related to the level and index of the field name. If you have two fields with the same level and index, only the first one is going to get exported...any subsequent ones will not.

    The solution in my case is to create a new field name or find the first one and hope it isn't being used.

+ Reply to Thread

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

     

Bookmarks

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts