I am using guid keys.



In a custom data source BO for a report I am putting a filter on a child cursor



Basically I want the filter to be "cclientkey =" and then the guid as a string - but of course in quotes



_policydisplay.SourceBO.Filter = "cclientkey = " & Me.ckey.ToString



doesn't work as the guid is not surrounded by quote in the resulting filter string.



I googled and tried things like



Dim quotes As Char = ChrW(34)

Dim filtstr As String = "cclientkey = " & quotes & Me.ckey.ToString & quotes

_policyDisplay.SourceBO.Filter = filtstr





Dim filtstr As String = "cclientkey = """ & Me.ckey.ToString & """"

_policyDisplay.SourceBO.Filter = filtstr



etc and no joy



Then reverted to the old Foxpro way



Dim filtstr as String = "cclientkey = '" & me.ckey.toString & "'" ( using single quotes to surround the guid )

and it works.



But a single quote to surround a string will throw and error. Is this some magic the old Foxers at Microfour have made possible? Never saw any solution like this in VB land? And what other ways are there to do this that work?

The code you gave me and works fine. I was just wondering why a single quote works surrounding the guid as I have usually found VB doesn't like single quotes (except as part of a string passed to a sql backend) and doesn't see them as an alternative to doublequote. You know what I mean about Foxpro, where you can use single quotes, double quotes or square brackets so putting quotes inside a string can be done a lot of different ways.



Since a BO filter is all within the BO I am surprised the VB compiler sees the single around the guid as defining a string where you could not say



Dim str as string = 'This is a string'

Now I understand, and yes you are right, unfortunately I don't know the answer, of course coming from VFP I also have been bit with this situation before.

Talking about VFP I had to release an update to one of my applications done in VFP and while coding I often used the single quote instead of the "*" to comment a line realizing that I was not coding in VB.NET , also I expected the IDE to properly format the code after finish a line without having to run the Beautify command.  It was a bit frustrating going back to the VFP IDE.

Edhy Rijo