Re: VFP/MySQL issue for private variables in SQL statement on Windows vs Linux backends

2006-11-08 Thread MB Software Solutions
Whil Hentzen (Pro*) wrote: > But this still doesn't explain why the same code worked locally but not > remotely. It WASs the same code, right? > > > Sure...same code, and I'm positive because of the approach I was using. I grabbed the SQL statement from my local meta-data DBF table, then exe

Re: VFP/MySQL issue for private variables in SQL statement on Windows vs Linux backends

2006-11-08 Thread Whil Hentzen (Pro*)
MB Software Solutions wrote: > Whil Hentzen (Pro*) wrote: > > > >>> Kevin's TEXTMERGE idea seems to have fit the bill perfectly, so no need >>> for that...but thanks anyway! >>> >> So what was the problem in the first place, that textmerge solved? >> > The textmerge substituted the val

Re: VFP/MySQL issue for private variables in SQL statement on Windows vs Linux backends

2006-11-08 Thread MB Software Solutions
Whil Hentzen (Pro*) wrote: >> Kevin's TEXTMERGE idea seems to have fit the bill perfectly, so no need >> for that...but thanks anyway! >> > > So what was the problem in the first place, that textmerge solved? > The textmerge substituted the values explicitly, so that resolved what was

Re: VFP/MySQL issue for private variables in SQL statement on Windows vs Linux backends

2006-11-08 Thread Whil Hentzen (Pro*)
>> What about knocking the SELECT down a bit - do it without a WHERE >> clause, or (if that would return too many rows) a hard-coded iAge = 37. >> Then add iAge = ?piAge. Then add one of the two date ends (dDate > >> ?pdBegDate. And so on... >> > Kevin's TEXTMERGE idea seems to have fit the b

Re: VFP/MySQL issue for private variables in SQL statement on Windows vs Linux backends

2006-11-08 Thread MB Software Solutions
Kevin Cully wrote: > I'd go with Plan B. I've never liked surprises, and I can debug easier > if I have the SPT all put together for me before I try to execute it. I > usually do a TEXTMERGE to get the values into the SPT. > I've used TEXT/ENDTEXT in the past, but that was on SPT built right

Re: VFP/MySQL issue for private variables in SQL statement on Windows vs Linux backends

2006-11-08 Thread MB Software Solutions
Whil Hentzen (Pro*) wrote: > > Well, there you go again. I heard that the folks who make WinXP have > been seen recently consorting with Communists. > Now hey, don't talk about Chet that waySenator McCarthy's legacy shouldn't continue, Whil! > >> select cname, iage, ddate from M

Re: VFP/MySQL issue for private variables in SQL statement on Windows vs Linux backends

2006-11-08 Thread Whil Hentzen (Pro*)
MB Software Solutions wrote: > App written in VFP9SP1. > My O/S: WinXP Pro Well, there you go again. I heard that the folks who make WinXP have been seen recently consorting with Communists. > > select cname, iage, ddate from MySQLTable where iAge = ?piAge and dDate > between ?pdBegDate

Re: VFP/MySQL issue for private variables in SQL statement on Windows vs Linux backends

2006-11-08 Thread Kevin Cully
I'd go with Plan B. I've never liked surprises, and I can debug easier if I have the SPT all put together for me before I try to execute it. I usually do a TEXTMERGE to get the values into the SPT. Kevin Cully CULLY Technologies, LLC Sponsor of Fox Forward 2006! http://foxforward.net MB Sof

VFP/MySQL issue for private variables in SQL statement on Windows vs Linux backends

2006-11-08 Thread MB Software Solutions
App written in VFP9SP1. My O/S: WinXP Pro MySQL database local version is 4.0.13-nt. MySQL web database version is 4.1.15-Debian_1-log. MyODBC driver version is MySQL ODBC 3.51. These SQL statements are stored in a local DBF lookup table and retrieved for SPT execution on the fly. Other: I'm wea