Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » DBISAM Technical Support » Support Forums » DBISAM General » View Thread |
Messages 1 to 2 of 2 total |
Guid Primary Keys and ODBC.NET |
Tue, Jan 1 2008 6:15 PM | Permanent Link |
"Bruce" | I am accessing DBISAM 4 tables under ADO.NET using the ODBC driver. The
tables use Guids for primary keys and relationships between tables. When I fill a DataSet using a DataAdpater, the DataType for these columns is reported as string. When I subsequently try to use lookup controls from DevExpress, the lookup does not work when the lookup relationship is based on these guid strings. Can someone help me understand what the issue is and what I can do to get this to work? Thanks... --Bruce |
Wed, Jan 2 2008 3:50 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Bruce,
<< I am accessing DBISAM 4 tables under ADO.NET using the ODBC driver. The tables use Guids for primary keys and relationships between tables. When I fill a DataSet using a DataAdpater, the DataType for these columns is reported as string. When I subsequently try to use lookup controls from DevExpress, the lookup does not work when the lookup relationship is based on these guid strings. Can someone help me understand what the issue is and what I can do to get this to work? >> DBISAM is correct - GUIDs in DBISAM are 38-byte string fields. I'm not sure what problem the DevExpress control is having, but you'll probably have to contact them to find out more. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Tuesday, April 30, 2024 at 03:55 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |