>
> Don't you just hate it when they label your app as the problem merely
> because it's Foxpro? BASTARDS!!!!!
>
Bastards indeed! After they "fixed" their interface they told my client
(who knows me well, and has seen me lock horns with others in the past with
technical issues where I have found defects/problems) they only altered
their app because I was being so uncooperative, and I never should have used
an outdated language ("total solution"? <g>) as Visual FoxPro since it was
dead, and VB6 was the ideal language to use for any serious development....
Hmmm... Their app locks up (even now) every few weeks, and needs to be
restarted, and their Access table based searches are slow. My stuff VFP
runs fast, and is up 24 x 7, never locked up, not once ever (Windows 2000
SP4).
When one of their installers was on site during all this controversy he
needed to do a conversion on his Access tables. He began to run his VB6
conversion against the Access affected table (over 400,000 records), and it
was poking along real slow. I asked him to kill his update process and let
me perform the conversion using VFP on an updateable view via ODBC. He
scoffed, so I told him the worst he could do is learn something, or better
yet he could torment me about my outdated VFP app if it did not run faster
than VB6. He agreed, and I wrote a simple STRTRAN('<string>', '-', '*') for
.t. piece of code, followed with tableupdate() of course. Wow! Even I was
shocked at the performance difference! Pow! It went so fast that he then
scanned every record in VB6 to make certain the data had actually been
changed without defect. He was impressed, but did not want to tell his
Support Techs on the phone that VFP just kicked their asses in performance,
as he thought he could lose his job for being uncooperative <g>...
Super-Bastards!
Gil
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] Behalf Of MB Software Solutions
> Sent: Friday, June 01, 2007 10:55 AM
> To: [EMAIL PROTECTED]
> Subject: Re: MySQL ODBC
>
>
> mrgmhale wrote:
> > The space padding is an issue I ran into using ODBC to connect to a M$
> > Access database table a few years ago. The designers of the VB
> app that I
> > was passing converted data to had a textbox of limited width, and right
> > justified and no value trimming. I will pulling a PartNo field from an
> > Access table via ODBC connectivity, performed a conversion on the PartNo
> > value, then sent the converted value to a target Access table
> used by the VB
> > app to import various data, including my converted PartNo data.
> With the
> > ODBC padding the PartNo value was getting pushed out of the
> display width
> > limitation of the right justified textbox. When I researched
> to cause of
> > the problem I found that ODBC intentionally performs the
> padding, and there
> > was no way around it. The VB app was eventually altered to populate the
> > offending textbox with a trimmed PartNo imported value, and a
> left justified
> > format - although the programmers had insisted right up to the
> end it was a
> > problem caused by me (cuz that crazy assed FoxPro stuff is a
> dead language,
> > you know!). When I finally gathered the documentation from M$
> showing it
> > was an intentional design for ODBC to work properly they ceded
> the point and
> > "fixed" what I deemed to be a poor interface issue on their part anyway
> > (lazy assed programming).
> >
> > So, unless something in a very basic concept in ODBC design has
> changed in
> > the past 6 years or so, then no, the padded values will not go
> away. I hate
> > being the bearer of bad tidings... But, I guess someone has to
> do it <g>...
> >
>
> Don't you just hate it when they label your app as the problem merely
> because it's Foxpro? BASTARDS!!!!!
>
> --
> Michael J. Babcock, MCP
> MB Software Solutions, LLC
> http://mbsoftwaresolutions.com
> http://fabmate.com
> "Work smarter, not harder, with MBSS custom software solutions!"
>
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** 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.
