GUID(Replication ID) Good or Bad??

[qajussi]

My client's Access database used the Guid(replication ID) as the data type. This is causing us great pain.
The problem is we have upgraded the access database to the SQL Server and left some of dynamic tables in the access tables.

We are manipulating the guid between the access tables and sql tables and they don't match in the some of the queries because the access keeps the guid with {guid{343434-3333..etc format) but sql server keeps {343433...ect without 'guid' in front.
We are using the StringFromGuid() and GuidFromString() but it is still very painful process because the access replication ids don't seem to behave consistently.
between access tables, we need to have 'guid'as prefixe but not between sql server tables.

Any advise on how to handle this and can you share your experiences with the guid??

Another question is that currently we are using the access forms but planning to convert all the access queries(pass through and all) to the store procedures and create webpages using asp.net.
Do you think we should get rid of the quids from the tables??
Thank you for your help.

 

[THWatson]

qajussi
Here is a link that might help you decide what to do.

http://support.microsoft.com/kb/q282977/

Tom

 

[THWatson]

qajussi
Here's another link that talks about a query not returning correct records with GUID.

http://support.microsoft.com/kb/q210612/

Tom