GUID not allowed in Find Method

  • Thread starter Thread starter Toni
  • Start date Start date
T

Toni

We are currently are using Access 2003 and going to start using SQL Server
2008.
We currently have one access application that links to the tables by using a
DSN connection The connection seems to work fine and for the most part the
application works. One problem that we are having is using some of the
dropdown combo box. The following error occurs "Run-time error '3614'": GUID
not allowed in Find Method criteria expression."

Below is the source code for the combo box.

Private Sub Combo3_AfterUpdate()
' Find the record that matches the control.
Me.RecordsetClone.FindFirst "[dbo_MemberList].[MemberID] = '" &
Me![Combo3] & "'"
Me.Bookmark = Me.RecordsetClone.Bookmark
End Sub

The value of me![Combo3] has the correct guid information

The only thing that has changed is we have changed the application to link
to the new DSN link The rest of our access applications are actual .adp apps
and they all work fine.

Any suggestions would be greatly appreciated.

Thanks in advance
Tsharp
 
I don't want to be rude but if it says that UID are not allowed with the
Find Method then I suppose that they are not allowed. You should try adding
a new field to the query used as the source for the form that will convert
the GUID into a string value (and use this field for your Find Method
expression).

Also, this newsgroup is about ADP and has nothing to do with either ODBC
Linked tables or DAO. You should try with a forum such as
m.p.access.odbclientsvr or - better in your case as you are dealing with a
DAO problem: m.p.a.modulesdaovba.

--
Sylvain Lafontaine, ing.
MVP - Windows Live Platform
Email: sylvain aei ca (fill the blanks, no spam please)
Independent consultant and remote programming for Access and SQL-Server
(French)
 
On Thu, 19 Feb 2009 03:20:35 -0500, "Sylvain Lafontaine"

Or, if indeed you are not using an ADP but linked tables, you can use
the StringFromGUID function to convert the column to string, and then
search that.
Avoiding GUIDs is an even better idea.

-Tom.
Microsoft Access MVP
 
Thanks to both of you, I realized this was not an .adp question, but was
unsure where to post my question, I mostly deal w/ .adp and have great
success with getting good answers to my questions. I tried using the
stringToGuid function but had no luck, so I added another column to the combo
and used that column to find my record and that worked. I guess I was a
little surprised that by going to SS2008 the application no longer worked...

Thanks again.
 
Back
Top