Jump to content


Best Learning Material

Books manuals learning

  • Please log in to reply
22 replies to this topic

#21 Jim Byram

Jim Byram
  • Moderators
  • 7,391 posts
  • Gender:Male
  • Location:Framingham, MA

Posted 02 November 2013 - 12:10 PM

Just remember that if TMG creates a new global tag type, you can rename that tag type.


You just need to do whatever gets the most data across and requires the least amount of post-import cleanup.


If there is an error that you can't resolve, you need to provide the data and step-by-step instructions so that we can look at it.

#22 mtnbluedatab

  • Members
  • 20 posts
  • Gender:Male
  • Location:Calgary, Alberta

Posted 02 November 2013 - 02:06 PM

Super, thanks for the support.

To aid in confirming data transfer, is there a higher level technique or report that shows all the data that the import function actually encountered and the resultant action? Or will I have to inspect all areas for which I expect to find such data?

#23 Jim Byram

Jim Byram
  • Moderators
  • 7,391 posts
  • Gender:Male
  • Location:Framingham, MA

Posted 03 November 2013 - 07:10 AM

Import is a two stage process.

1) Genbridge imports the data from the source database in a text data stream.

2) This data stream is processed by TMG (using the appropriate app) and the data is added to a new TMG project (or appended to an existing project).


I don't know if the data stream is directed to a temporary text file or if it is processed in memory. If a text file is created, it will be located in the TMG session folder located in the system temp folder. You would need to copy the file from the temp folder while the session is active.


I have debugging tools to create the intermediate GenBridge text file containing the data stream. The procedure for doing this is fairly obscure. You might ask Support for the GenBridge development kit.


The GenBridge text file just shows you what GenBridge has processed. It does not tell you how the data is going to be saved in the project that will be created by the import.


The only reason that I use the GenBridge debugging tools is to identify errors in the GenBridge process. Seeing what and how data is imported is best done by comparing the data in the source database to the data in the TMG project resulting from the import.


Import is an imperfect process. Only data that fits the TMG data model will be imported.

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users