Ok sorry to bother everyone, this is no longer a problem and never was an SQL problem.
The cloud provider the client was using got hacked with ransomware 3 days before Christmas and shut down the entire operation and all the companies that were running on their servers. The original ransom was $3 million so we assumed everything was done at that cloud provider. We had good backups of the SQL data but they did not have backups for the supporting config files mostly still DBF files ... It took several days to get new AWS servers setup and configured and the SQL data restored. Since we lost most of the config files we were guessing at the setup and somehow there is a setting that limits the string length of the return messages coming from my VFP9 app. When they setup the new AWS servers they installed SQL 2016 and we assumed there must be a problem since we did not have the problem on the SQL 2012 on the old servers. You know what they say about assuming. So the cloud provider somehow talked the hackers into reducing the ransom to $50,000 and they paid it 2 days after Christmas. Since we where having so many problems getting the new AWS servers up and running, we went back to the old servers and transferred all the IP's back to the old servers and they were back in business. So we have been working the last week or so trying to find a solution to get the VFP9 app to run correctly on the AWS servers with SQL 2016. Turns out it was never a problem and just a setting that was not entered correctly in the VFP9 app. Thanks for your help and long live the FOX !! This app has been running strong since 2002, that is 20 years of processing gift and reward cards 24/7 !! ----- Original Message ----- From: "Richard Kaye" <rk...@invaluable.com> To: "ProFox Email List" <profox@leafe.com> Sent: Wednesday, January 5, 2022 6:30:24 PM Subject: Re: VFP9 and SQL memo fields Not trying to be obnoxious here but installing a driver on its own won’t change anything. 😊 Has the connection string for the application been changed to use 17? I don’t think there is an “ODBC Driver 11 for SQL Server” but I could be wrong. There’s definitely a 13 and a 17. There is also “SQL Server Native Client 11.0”. Is it possible to use ODBC Manager in the environment in question to create a connection to the SQL Server the EXE uses? If that works, then you know the problem lies in the application configuration. -- rk From: ProfoxTech <profoxtech-boun...@leafe.com<mailto:profoxtech-boun...@leafe.com>> On Behalf Of kbe...@mchsi.com<mailto:kbe...@mchsi.com> Sent: Wednesday, January 5, 2022 5:39 PM To: profoxt...@leafe.com<mailto:profoxt...@leafe.com> Subject: Re: VFP9 and SQL memo fields I am pretty sure we are using Microsoft ODBC Driver 11 for SQL Server I think they tried to install ODBC Driver 17 and had the same results ----- Original Message ----- From: "Richard Kaye" <rk...@invaluable.com<mailto:rk...@invaluable.com>> To: "ProFox Email List" <profox@leafe.com<mailto:profox@leafe.com>> Sent: Wednesday, January 5, 2022 8:43:26 AM Subject: RE: VFP9 and SQL memo fields Do you know what SQL driver your EXE is currently using? -- rk From: ProfoxTech <profoxtech-boun...@leafe.com<mailto:profoxtech-boun...@leafe.com>> On Behalf Of kbe...@mchsi.com<mailto:kbe...@mchsi.com> Sent: Tuesday, January 4, 2022 8:48 PM To: profoxt...@leafe.com<mailto:profoxt...@leafe.com> Subject: Re: VFP9 and SQL memo fields Yes it is a compiled EXE for a legacy app that has been running great for years. I am using West-Wind wwSQL class to execute Queries and Stored procedures. I don't think it is remote views. I call the method and it returns a cursor or an oData object. I hope that helps as I am not an SQL expert. [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: https://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: https://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: https://leafe.com/archives This message: https://leafe.com/archives/byMID/1351208503.102444008.1641435858808.javamail.zim...@mchsi.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
