Alright - a final follow-up. OK - as previously mentioned - my systems guy said I should only connect to a Database if it's in Principal mode and Not in Mirror mode.
So, to test this out - I connected into the Albany server using MSSM Studio. And, when I went to look at one of the Databases in particular - I saw that it had the status of Mirror. Where as, in another session of MSSM Studio - I logged into our NYC Server - and the same Database had the mode of Pricipal. Sure, that's all well and good - and what I expected. Then I tried connecting to the Albany Server - and to that particular Database - using the same login credentials I used in MSSM Studio. Upon running that SQLSTRINGCONNECT statement - it returned a value of "-1" as the statement handle. So - my assumption is that - even though the SQLSTRINGCONNECT could connect to the Server, and could "See" the Database in question - it "knew" to return back a value of "-1" since the Database was in Mirror mode - and should thus NOT be used. Am I right? I suspect in this case - my assumption is correct. But, figured I should just get verification from those folks more knowledgeable in this area than myself (a kind of newbie for some of this SQL stuff)... Thanks again, -K- -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Kurt Wendt Sent: Friday, July 24, 2015 11:19 AM To: [email protected] Subject: RE: Connecting to SQL via VFP w/Failover... OK - U ProFoxers have Done it AGAIN! I got the problem solved. Although - will mention 1 thing didn't work as I expected it. I ran the following command: qProp_Set=SQLSETPROP(0, "DispWarnings", .F.) And, yet, when I ran the following command - I still got the Error screen: St_Hndl=SQLSTRINGCONNECT(lpconnstring, .T.) However, I was excited to find out that if I ran THIS Command: qProp_Set=SQLSETPROP(0, "DispLogin", 3) && 3 = Dont Prompt! It now DID Indeed work - the SQLSTRINGCONNECT command ran, and control returned back to VFP - with NO Pop-up screens, and instead the var. St_Hndl simply contained a value of -1. Awesome! Thanks again, -K- -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Kurt Wendt Sent: Friday, July 24, 2015 10:24 AM To: [email protected] Subject: RE: Connecting to SQL via VFP w/Failover... Thanks Fernando. RK suggested looking at the topic - Managing Connections with SQL Pass-Through - and when I found that help topic - literally the top section is all about the SQLSetProp command. Sounds like THAT WILL do what I need to do. I will check it out - and then follow-up here again... Thanks again - ProFox to the Rescue! -K- -----Original Message----- From: ProfoxTech [mailto:[email protected]] On Behalf Of Fernando D. Bozzo Sent: Friday, July 24, 2015 10:15 AM To: [email protected] Subject: Re: Connecting to SQL via VFP w/Failover... Hi Kurt If you use SQLSETPROP( mHandle, "DispLogin", 3 ) you shouldn't see a login scren, and should be able to catch the error. Regards.- --- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html --- [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/80838f1ca795b14ea1af48659f35166f1ce...@drexch02.corp.globetax.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.
