Why do GUIDs have curly brackets when read using the ODBC driver?
Question asked by Stan Paulauskas - 4/6/2022 at 8:11 AM
I'm using Atrex 19, and am pulling data out of the tables for inclusion in reports. I'm finding GUID fields are being returned with curly brackets around the GUID. For example: 

I'm finding this to be consistent regardless of the program used to access the data (Python, Microstrategy, etc.). 

Is this how the GUIDs are stored in the database, or am I getting the extra characters from somewhere else?

1 Reply

Reply to Thread
Mark Culos Replied
Employee Post Marked As Answer

This is how the GUID is stored in the database.

Reply to Thread