Developer
Developer at UltraDNT.com
Wed Mar 24 11:30:55 CST 2004
Yes, they are but, specifically, on an Access-2K2 FE to SQL-2K BE, I had a customer table, and I wanted a result set with 4 different FK's joined in, to see the "friendly" names of the customer properties (region, business type, etc.). This inherited database had guid's for primary keys in everything, even these nearly-static tables like business type. The Access query (joining the linked tables) had nulls in many of the cells, but returned the right data in some places, while a view I created on the server correctly filled in all the data. I did NO investigation on it, I just linked to the view and went on with life! Steve -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock Sent: Wednesday, March 24, 2004 11:56 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] OT: Migration to SQL Server - sort of Hi Developer How's that? Aren't GUIDs, at the table level, nothing more than strings? /gustav > Not exactly migration, but biggest issue I've had lately with Access > FE's to SQL 2k is that Access can't deal with GUID's. You *must* make > all the queries that join on these types of fields into views because > Access can't relaibly make these joins. -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com