You’re offline. This is a read only version of the page.
175
We have some customers that have apostrophes in their names. And when we set up a customer card with the correct spelling the apostrophe and do a lookup/open on the card SQL Server can't perform the action becase the apostrophe was not escaped.
[Microsoft][ODBC SQL Server Driver][SQL Server]Line 1: Incorrect syntax near 'ULA'.
[Microsoft][ODBC SQL Server Driver][SQL Server]Unclosed quotation mark before the character string ') ORDER BY SOPNUMBE ASC ,SOPTYPE ASC '.
This, as far as I know, was not a problem for us in the past. We just upgraded to GP 10 from GP 9. I looked in customer source and saw 3 similar but not exact help topics. They pointed to GP admin/setup controls. However, upon clicking around in the administration settings I don't see an obvious solution to this.
Is there a setup setting that needs to be turned on to handle this? Or, is the fix done somewhere else?
Surely GP 10 can handle apostrophe in customer cards. We don't want to escape them and then have the escape character show up in address labels, invoices, etc.
Thanks.
*This post is locked for comments
I have the same question (0)
I would be VERY surprised if this was a bug in GP. It's more often a problem with 3rd party products or customizations added to the system.
In my early days of customizing GP (2000) when SQL Server was still a new thing with GP, I too made this mistake of not replacing single quotes with 2 single quotes, which tells SQL Server to not freak out with the query, but with a little experience one learns to consistently use the REPLACE function whenever filtering by a string value.
The good folks at Great Plains (and subsequently Microsoft) learned this long before I, and don't usually make that mistake. But other "wet behind the ears" developers still do.
I would suggest checking to see if you have any Modifier/VBA customs installed (Microsoft Dynamcis GP>>Tools>>Customize>>Customization Maintenance). If so, and if VBA is added to the window causing the error, one of those could be the culprit. Otherwise, I would suggest disabling 3rd party products one by one using the Customization Status window (Microsoft Dynamcis GP>>Tools>>Customize>>Customization Status), testing after each disable, to see if you can find the issue.
Also, check security to make sure that whatever window you're using is a Microsoft window, and not some third party product version of the window.
Ron Draganowski
Share
Report
All responses (
Answers (
