mysql with vb 4.0

(Please cc: me as I am not subscribed)

I have a client with accounting software written in VB4.0. Even though
the company that wrote the software is still in business (and
apparently going strong), they have not yet got around to updating the
app to 32-bit VB. No, really. Stop laughing, it's not funny! :-P

Anywho, my clients want to do the whole 'web' thing they've been
hearing about, and have hired a programmer, chosen MySQL and PHP as
their technologies of choice, and are ready and raring to go. Except
for the whole "can't connect to the database from the
accounting/inventory/pos software"-angle. So, any ideas or
suggestions on how to get a 16-bit odbc driver for VB4? Or alternative
methods of making this work? Any and all ideas will be considered,
except for throwing away the old and moldy junk. They've been using
it for most of 10 years, and see no need to change.

To recap: VB4 software running on windows, connecting over the network
to linux server running apache/php/mysql.

D.A.Bishop


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: mysql with vb 4.0

David,

Forgive me, but this *is* funny :) However, I can see how it is not at
all funny from your perspective. I think it was Mel Brooks who said
(roughly) "if I cut my finger, that's tragedy, if you fall in a hole and
break your leg, that's comedy".

Some things you might have considered:(1) writing a 16 bit ODBC driver;
(2) creating a bridge between the web system and the old stuff.

(1) will probably require a 16 bit compiler (which might not want to
install anymore??). You should be able to use sockets to move data
between the 16 and 32 bit worlds. Watch out for security concerns. It
is unlikely that somebody would figure out how to connect and cause
trouble, but you must assume they will try. If nothing else, you have
to protect against innocent activity that might accidentally connect and
cause your code to do something bad.

(2) Re creating a bridge, and continuing with the socket idea above, you
will have trouble keeping things in synch. Anything that starts out as
"MySQL and PHP" is going to rely on the database for locking (yes, there
are other ways: ORBs come to mind), and that will be interesting to get
right.

To be honest, IMHO, the VB4 stuff needs to be rewritten. It will take
much more effort to reliably bridge between it and something new than it
will to just start over and write it cleanly using good OO tools,
especially given that they already know what they want for
functionality. I suspect you already know that.

Good luck,

Bill




Wilhelm K. Schwab, Ph.D.
University of Florida
Department of Anesthesiology
PO Box 100254
Gainesville, FL 32610-0254

Email: bills@anest4.anest.ufl.edu
Tel: (352) 846-1285
FAX: (352) 392-7029

>>> David Bishop 02/06/05 4:43 PM >>>
(Please cc: me as I am not subscribed)

I have a client with accounting software written in VB4.0. Even though
the company that wrote the software is still in business (and
apparently going strong), they have not yet got around to updating the
app to 32-bit VB. No, really. Stop laughing, it's not funny! :-P

Anywho, my clients want to do the whole 'web' thing they've been
hearing about, and have hired a programmer, chosen MySQL and PHP as
their technologies of choice, and are ready and raring to go. Except
for the whole "can't connect to the database from the
accounting/inventory/pos software"-angle. So, any ideas or
suggestions on how to get a 16-bit odbc driver for VB4? Or alternative
methods of making this work? Any and all ideas will be considered,
except for throwing away the old and moldy junk. They've been using
it for most of 10 years, and see no need to change.

To recap: VB4 software running on windows, connecting over the network
to linux server running apache/php/mysql.

D.A.Bishop


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe:
http://lists.mysql.com/win32?unsub=BSchwab@anest.ufl.edu



--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

RE: mysql with vb 4.0

Updating to 32-bit VB should be pretty straight-forward unless there are
non-standard libraries or something. I would have thought this is the
easiest approach. It's only going to become more of a problem as time
goes by.

John Bonnett

-----Original Message-----
From: David Bishop [mailto:teancom@gmail.com]=20
Sent: Monday, 7 February 2005 8:13 AM
To: win32@lists.mysql.com
Subject: mysql with vb 4.0

(Please cc: me as I am not subscribed)

I have a client with accounting software written in VB4.0. Even though=20
the company that wrote the software is still in business (and=20
apparently going strong), they have not yet got around to updating the=20
app to 32-bit VB. No, really. Stop laughing, it's not funny! :-P

Anywho, my clients want to do the whole 'web' thing they've been=20
hearing about, and have hired a programmer, chosen MySQL and PHP as=20
their technologies of choice, and are ready and raring to go. Except=20
for the whole "can't connect to the database from the=20
accounting/inventory/pos software"-angle. So, any ideas or=20
suggestions on how to get a 16-bit odbc driver for VB4? Or alternative=20
methods of making this work? Any and all ideas will be considered,=20
except for throwing away the old and moldy junk. They've been using=20
it for most of 10 years, and see no need to change.

To recap: VB4 software running on windows, connecting over the network=20
to linux server running apache/php/mysql.

D.A.Bishop


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

Re: mysql with vb 4.0

Well, that's up to the company that sold my clients the software in the
first place. And they claim that they will be releasing a 32-bit
version in Q2 of this year, but then, they claimed the same thing last
year. And I believe the year before that...

On Feb 6, 2005, at 3:44 PM, John Bonnett, R&D Australia wrote:

> Updating to 32-bit VB should be pretty straight-forward unless there
> are
> non-standard libraries or something. I would have thought this is the
> easiest approach. It's only going to become more of a problem as time
> goes by.
>
> John Bonnett
>
> -----Original Message-----
> From: David Bishop [mailto:teancom@gmail.com]
> Sent: Monday, 7 February 2005 8:13 AM
> To: win32@lists.mysql.com
> Subject: mysql with vb 4.0
>
> (Please cc: me as I am not subscribed)
>
> I have a client with accounting software written in VB4.0. Even though
> the company that wrote the software is still in business (and
> apparently going strong), they have not yet got around to updating the
> app to 32-bit VB. No, really. Stop laughing, it's not funny! :-P
>
> Anywho, my clients want to do the whole 'web' thing they've been
> hearing about, and have hired a programmer, chosen MySQL and PHP as
> their technologies of choice, and are ready and raring to go. Except
> for the whole "can't connect to the database from the
> accounting/inventory/pos software"-angle. So, any ideas or
> suggestions on how to get a 16-bit odbc driver for VB4? Or alternative
> methods of making this work? Any and all ideas will be considered,
> except for throwing away the old and moldy junk. They've been using
> it for most of 10 years, and see no need to change.
>
> To recap: VB4 software running on windows, connecting over the network
> to linux server running apache/php/mysql.
>
> D.A.Bishop
>


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: mysql with vb 4.0

Oh, I fully realize this is chuckle-worthy for anyone not affected.
And the actual quote is 'Tragedy is when I cut my finger. Comedy is
when you walk into an open sewer and die.' Well, I'm dying :-)

1) Is out of my league. Maybe it's within the skillset of the
programmer they hired to code the webapp, but knowing the skillset of
most webapp guys, probably not (that's not a slam on webapp guys, btw,
since I can't do it either :-). I'll check on that.

2) Is something they've considered, hiring someone from the company
that wrote the original software to do some sort of middleware. Of
course, these guys have (apparently) been sitting around playing with
themselves for the last 7 years, so who knows if they can still code
(their RSI is probably horrendous).

3) (complete rewrite) is verboten. They are content to wait for the
next release to come down like manna from heaven, and are adjusted to
the fact that nothing they do will speed up the process, or affect it
in any way. I have another client that I just convinced to move off of
the same software, and it took all of my geek powers of convincing to
do the job, and they had a much smaller install.

I think I'm going to go find an open sewer...

David

On Feb 6, 2005, at 3:43 PM, Bill Schwab wrote:

> David,
>
> Forgive me, but this *is* funny :) However, I can see how it is not at
> all funny from your perspective. I think it was Mel Brooks who said
> (roughly) "if I cut my finger, that's tragedy, if you fall in a hole
> and
> break your leg, that's comedy".
>
> Some things you might have considered:(1) writing a 16 bit ODBC driver;
> (2) creating a bridge between the web system and the old stuff.
>
> (1) will probably require a 16 bit compiler (which might not want to
> install anymore??). You should be able to use sockets to move data
> between the 16 and 32 bit worlds. Watch out for security concerns. It
> is unlikely that somebody would figure out how to connect and cause
> trouble, but you must assume they will try. If nothing else, you have
> to protect against innocent activity that might accidentally connect
> and
> cause your code to do something bad.
>
> (2) Re creating a bridge, and continuing with the socket idea above,
> you
> will have trouble keeping things in synch. Anything that starts out as
> "MySQL and PHP" is going to rely on the database for locking (yes,
> there
> are other ways: ORBs come to mind), and that will be interesting to get
> right.
>
> To be honest, IMHO, the VB4 stuff needs to be rewritten. It will take
> much more effort to reliably bridge between it and something new than
> it
> will to just start over and write it cleanly using good OO tools,
> especially given that they already know what they want for
> functionality. I suspect you already know that.
>
> Good luck,
>
> Bill
>
>
>
>
> Wilhelm K. Schwab, Ph.D.
> University of Florida
> Department of Anesthesiology
> PO Box 100254
> Gainesville, FL 32610-0254
>
> Email: bills@anest4.anest.ufl.edu
> Tel: (352) 846-1285
> FAX: (352) 392-7029
>
>>>> David Bishop 02/06/05 4:43 PM >>>
> (Please cc: me as I am not subscribed)
>
> I have a client with accounting software written in VB4.0. Even though
> the company that wrote the software is still in business (and
> apparently going strong), they have not yet got around to updating the
> app to 32-bit VB. No, really. Stop laughing, it's not funny! :-P
>
> Anywho, my clients want to do the whole 'web' thing they've been
> hearing about, and have hired a programmer, chosen MySQL and PHP as
> their technologies of choice, and are ready and raring to go. Except
> for the whole "can't connect to the database from the
> accounting/inventory/pos software"-angle. So, any ideas or
> suggestions on how to get a 16-bit odbc driver for VB4? Or alternative
> methods of making this work? Any and all ideas will be considered,
> except for throwing away the old and moldy junk. They've been using
> it for most of 10 years, and see no need to change.
>
> To recap: VB4 software running on windows, connecting over the network
> to linux server running apache/php/mysql.
>
> D.A.Bishop
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
> http://lists.mysql.com/win32?unsub=BSchwab@anest.ufl.edu
>
>


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

RE: mysql with vb 4.0

In the early days of 32-bit programming there was/is something called
'thunking' this allowed for a mixture of 32 and 16-bit programs
communicating (Microsoft had both types of programs/modules running together
in the beginning). To solve this problem a 'thunk' could be built to allow
VB4 application to call a DLL that would handle the interface with MySQL.

I will agree that it would be far easier and cheaper updating the VB4 app.
to 32-bit VB.

Bob.

-----Original Message-----
From: David Bishop [mailto:teancom@gmail.com]
Sent: Sunday, February 06, 2005 4:43 PM
To: win32@lists.mysql.com
Subject: mysql with vb 4.0

(Please cc: me as I am not subscribed)

I have a client with accounting software written in VB4.0. Even though
the company that wrote the software is still in business (and
apparently going strong), they have not yet got around to updating the
app to 32-bit VB. No, really. Stop laughing, it's not funny! :-P

Anywho, my clients want to do the whole 'web' thing they've been
hearing about, and have hired a programmer, chosen MySQL and PHP as
their technologies of choice, and are ready and raring to go. Except
for the whole "can't connect to the database from the
accounting/inventory/pos software"-angle. So, any ideas or
suggestions on how to get a 16-bit odbc driver for VB4? Or alternative
methods of making this work? Any and all ideas will be considered,
except for throwing away the old and moldy junk. They've been using
it for most of 10 years, and see no need to change.

To recap: VB4 software running on windows, connecting over the network
to linux server running apache/php/mysql.

D.A.Bishop


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=bobingra@bellsouth.net


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: mysql with vb 4.0

Is there a reason you can't just take the source code for the VB4
application and build it in VB6? I highly doubt that much of Visual Basic
has changed. Even if it required a little work, you could probably contract
it out cheaply.

If you were absolutely stuck on VB4, you could develop a data exchange
system to bridge the 16bit to 32bit gap by using TCP to communicate with an
intermediate server program that would act as your MySQL client. So you
write a 32bit server program which talks to MySQL for you, and you send your
requests to the 32bit program. That's probably how I'd handle that. I'm
not sure about accessing Winsock in a 16bit VB application, but they may
have an old socket control.

But with such a simple language as Visual Basic, I don't doubt that you
could compile it for 32bit in VB6 without much of a problem. Have you
tried?


----- Original Message -----
From: "Bob Ingram"
To: "David Bishop" ;
Sent: Sunday, February 06, 2005 4:28 PM
Subject: RE: mysql with vb 4.0


> In the early days of 32-bit programming there was/is something called
> 'thunking' this allowed for a mixture of 32 and 16-bit programs
> communicating (Microsoft had both types of programs/modules running
> together
> in the beginning). To solve this problem a 'thunk' could be built to allow
> VB4 application to call a DLL that would handle the interface with MySQL.
>
> I will agree that it would be far easier and cheaper updating the VB4 app.
> to 32-bit VB.
>
> Bob.
>
> -----Original Message-----
> From: David Bishop [mailto:teancom@gmail.com]
> Sent: Sunday, February 06, 2005 4:43 PM
> To: win32@lists.mysql.com
> Subject: mysql with vb 4.0
>
> (Please cc: me as I am not subscribed)
>
> I have a client with accounting software written in VB4.0. Even though
> the company that wrote the software is still in business (and
> apparently going strong), they have not yet got around to updating the
> app to 32-bit VB. No, really. Stop laughing, it's not funny! :-P
>
> Anywho, my clients want to do the whole 'web' thing they've been
> hearing about, and have hired a programmer, chosen MySQL and PHP as
> their technologies of choice, and are ready and raring to go. Except
> for the whole "can't connect to the database from the
> accounting/inventory/pos software"-angle. So, any ideas or
> suggestions on how to get a 16-bit odbc driver for VB4? Or alternative
> methods of making this work? Any and all ideas will be considered,
> except for throwing away the old and moldy junk. They've been using
> it for most of 10 years, and see no need to change.
>
> To recap: VB4 software running on windows, connecting over the network
> to linux server running apache/php/mysql.
>
> D.A.Bishop
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe:
> http://lists.mysql.com/win32?unsub=bobingra@bellsouth.net
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=jgowdy@cox.net
>
>


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: mysql with vb 4.0

Something that I probably didn't make clear enough is that the app in
question is a third-party binary app that my clients purchased. They
don't have the source code, so we can't just recompile it. Otherwise
I'd definetly be going down that road.

On Feb 6, 2005, at 9:37 PM, Jeremiah Gowdy wrote:

> Is there a reason you can't just take the source code for the VB4
> application and build it in VB6? I highly doubt that much of Visual
> Basic has changed. Even if it required a little work, you could
> probably contract it out cheaply.
>
> If you were absolutely stuck on VB4, you could develop a data exchange
> system to bridge the 16bit to 32bit gap by using TCP to communicate
> with an intermediate server program that would act as your MySQL
> client. So you write a 32bit server program which talks to MySQL for
> you, and you send your requests to the 32bit program. That's probably
> how I'd handle that. I'm not sure about accessing Winsock in a 16bit
> VB application, but they may have an old socket control.
>
> But with such a simple language as Visual Basic, I don't doubt that
> you could compile it for 32bit in VB6 without much of a problem. Have
> you tried?
>
>
> ----- Original Message ----- From: "Bob Ingram"
>
> To: "David Bishop" ;
> Sent: Sunday, February 06, 2005 4:28 PM
> Subject: RE: mysql with vb 4.0
>
>
>> In the early days of 32-bit programming there was/is something called
>> 'thunking' this allowed for a mixture of 32 and 16-bit programs
>> communicating (Microsoft had both types of programs/modules running
>> together
>> in the beginning). To solve this problem a 'thunk' could be built to
>> allow
>> VB4 application to call a DLL that would handle the interface with
>> MySQL.
>>
>> I will agree that it would be far easier and cheaper updating the VB4
>> app.
>> to 32-bit VB.
>>
>> Bob.
>>
>> -----Original Message-----
>> From: David Bishop [mailto:teancom@gmail.com]
>> Sent: Sunday, February 06, 2005 4:43 PM
>> To: win32@lists.mysql.com
>> Subject: mysql with vb 4.0
>>
>> (Please cc: me as I am not subscribed)
>>
>> I have a client with accounting software written in VB4.0. Even
>> though
>> the company that wrote the software is still in business (and
>> apparently going strong), they have not yet got around to updating the
>> app to 32-bit VB. No, really. Stop laughing, it's not funny! :-P
>>
>> Anywho, my clients want to do the whole 'web' thing they've been
>> hearing about, and have hired a programmer, chosen MySQL and PHP as
>> their technologies of choice, and are ready and raring to go. Except
>> for the whole "can't connect to the database from the
>> accounting/inventory/pos software"-angle. So, any ideas or
>> suggestions on how to get a 16-bit odbc driver for VB4? Or
>> alternative
>> methods of making this work? Any and all ideas will be considered,
>> except for throwing away the old and moldy junk. They've been using
>> it for most of 10 years, and see no need to change.
>>
>> To recap: VB4 software running on windows, connecting over the network
>> to linux server running apache/php/mysql.
>>
>> D.A.Bishop
>>
>>
>> --
>> MySQL Windows Mailing List
>> For list archives: http://lists.mysql.com/win32
>> To unsubscribe:
>> http://lists.mysql.com/win32?unsub=bobingra@bellsouth.net
>>
>>
>> --
>> MySQL Windows Mailing List
>> For list archives: http://lists.mysql.com/win32
>> To unsubscribe: http://lists.mysql.com/win32?unsub=jgowdy@cox.net
>>
>


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

RE: mysql with vb 4.0

Just another thought:

You could take the source code for the VBMySQLDirect (www.vbmysql.com) =
component and using some thunking to talk to libmysql.dll, use that =
instead?=20
There's some stuff for VB3 (!) here http://www.arcatapet.net/vb.cfm, a =
bit frm Microsoft here =
http://support.microsoft.com/default.aspx?scid=3DKB;en-us;14 1939 and =
here's a free dll for calling 32 bit dll's from a 16 bit app: =
http://www.programmersheaven.com/zone15/cat161/17100.htm.

Don't know if this is of any use, but ....

Andy


-----Original Message-----
From: David Bishop [mailto:teancom@gmail.com]
Sent: 07 February 2005 05:37
To:
Subject: Re: mysql with vb 4.0



Something that I probably didn't make clear enough is that the app in=20
question is a third-party binary app that my clients purchased. They=20
don't have the source code, so we can't just recompile it. Otherwise=20
I'd definetly be going down that road.

On Feb 6, 2005, at 9:37 PM, Jeremiah Gowdy wrote:

> Is there a reason you can't just take the source code for the VB4=20
> application and build it in VB6? I highly doubt that much of Visual=20
> Basic has changed. Even if it required a little work, you could=20
> probably contract it out cheaply.
>
> If you were absolutely stuck on VB4, you could develop a data exchange =

> system to bridge the 16bit to 32bit gap by using TCP to communicate=20
> with an intermediate server program that would act as your MySQL=20
> client. So you write a 32bit server program which talks to MySQL for=20
> you, and you send your requests to the 32bit program. That's probably =

> how I'd handle that. I'm not sure about accessing Winsock in a 16bit=20
> VB application, but they may have an old socket control.
>
> But with such a simple language as Visual Basic, I don't doubt that=20
> you could compile it for 32bit in VB6 without much of a problem. Have =

> you tried?
>
>
> ----- Original Message ----- From: "Bob Ingram"=20
>
> To: "David Bishop" ;
> Sent: Sunday, February 06, 2005 4:28 PM
> Subject: RE: mysql with vb 4.0
>
>
>> In the early days of 32-bit programming there was/is something called
>> 'thunking' this allowed for a mixture of 32 and 16-bit programs
>> communicating (Microsoft had both types of programs/modules running=20
>> together
>> in the beginning). To solve this problem a 'thunk' could be built to=20
>> allow
>> VB4 application to call a DLL that would handle the interface with=20
>> MySQL.
>>
>> I will agree that it would be far easier and cheaper updating the VB4 =

>> app.
>> to 32-bit VB.
>>
>> Bob.
>>
>> -----Original Message-----
>> From: David Bishop [mailto:teancom@gmail.com]
>> Sent: Sunday, February 06, 2005 4:43 PM
>> To: win32@lists.mysql.com
>> Subject: mysql with vb 4.0
>>
>> (Please cc: me as I am not subscribed)
>>
>> I have a client with accounting software written in VB4.0. Even=20
>> though
>> the company that wrote the software is still in business (and
>> apparently going strong), they have not yet got around to updating =
the
>> app to 32-bit VB. No, really. Stop laughing, it's not funny! :-P
>>
>> Anywho, my clients want to do the whole 'web' thing they've been
>> hearing about, and have hired a programmer, chosen MySQL and PHP as
>> their technologies of choice, and are ready and raring to go. Except
>> for the whole "can't connect to the database from the
>> accounting/inventory/pos software"-angle. So, any ideas or
>> suggestions on how to get a 16-bit odbc driver for VB4? Or=20
>> alternative
>> methods of making this work? Any and all ideas will be considered,
>> except for throwing away the old and moldy junk. They've been using
>> it for most of 10 years, and see no need to change.
>>
>> To recap: VB4 software running on windows, connecting over the =
network
>> to linux server running apache/php/mysql.
>>
>> D.A.Bishop
>>
>>
>> --
>> MySQL Windows Mailing List
>> For list archives: http://lists.mysql.com/win32
>> To unsubscribe:=20
>> http://lists.mysql.com/win32?unsub=3Dbobingra@bellsouth.net
>>
>>
>> --=20
>> MySQL Windows Mailing List
>> For list archives: http://lists.mysql.com/win32
>> To unsubscribe: =
http://lists.mysql.com/win32?unsub=3Djgowdy@cox.net
>>
>


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=3Dgcdmw-win32@m.gmane.org

Re: mysql with vb 4.0

On 6 Feb 2005 at 14:43, David Bishop wrote:



> Anywho, my clients want to do the whole 'web' thing they've been
> hearing about, and have hired a programmer, chosen MySQL and PHP as
> their technologies of choice, and are ready and raring to go. Except
> for the whole "can't connect to the database from the
> accounting/inventory/pos software"-angle. So, any ideas or
> suggestions on how to get a 16-bit odbc driver for VB4? Or
> alternative methods of making this work? Any and all ideas will be
> considered, except for throwing away the old and moldy junk. They've
> been using it for most of 10 years, and see no need to change.



Hi David,

When you say *connect VB4 to mysql* are you saying you want to export your
accounting data from the VB4 app to the mysql database?

In what format is the data stored at the moment?

Does the app currently allow you to export the data? If so what formats are
available?

Regards

Ian
--


--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: mysql with vb 4.0

Maybe I'm getting it wrong, but you don't wanna mess with the app that
your client uses, you want to access the database that your old app
uses and deal with the data, if you can discover what kind of database
is used by your old app as storage, you can try to convert it to MySQL
and access it directly with PHP (no ODBC needed). You may wanna find a
PHP driver for the exact database your using and even avoid the MySQL
conversion (don't look at me, you SHOULD use MySQL, but you can't
convert the database every time it changes). There is no way you can
mess with the 16 bits app without messing with copyright issues (you
mentioned you don't have the source code).

You may use another approuch, by using a CGI app to access and deal
with the data and return values to a web page. In fact, there are
thousands of solutions, but you do need to discover the storage engine
the old app uses, and you need to create an "interface" between the
database and the web.

PS: At the time they wrote the app, DB2 databases where in large use,
I bet that is the storage engine.

OBS: Spread MySQL and make the guy that wrote the app uses it :) it
would be just perfect.

Best regards,

On Wed, 09 Feb 2005 11:29:07 -0000, Ian Gibbons wrote:
> On 6 Feb 2005 at 14:43, David Bishop wrote:
>
>
>
> > Anywho, my clients want to do the whole 'web' thing they've been
> > hearing about, and have hired a programmer, chosen MySQL and PHP as
> > their technologies of choice, and are ready and raring to go. Except
> > for the whole "can't connect to the database from the
> > accounting/inventory/pos software"-angle. So, any ideas or
> > suggestions on how to get a 16-bit odbc driver for VB4? Or
> > alternative methods of making this work? Any and all ideas will be
> > considered, except for throwing away the old and moldy junk. They've
> > been using it for most of 10 years, and see no need to change.
>
>
>
> Hi David,
>
> When you say *connect VB4 to mysql* are you saying you want to export your
> accounting data from the VB4 app to the mysql database?
>
> In what format is the data stored at the moment?
>
> Does the app currently allow you to export the data? If so what formats are
> available?
>
> Regards
>
> Ian
> --
>
>
> --
> MySQL Windows Mailing List
> For list archives: http://lists.mysql.com/win32
> To unsubscribe: http://lists.mysql.com/win32?unsub=danieldaveiga@gmail.com
>
>


--
Daniel da Veiga
Computer Operator - RS - Brazil

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: mysql with vb 4.0

--Apple-Mail-3-853089471
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=WINDOWS-1252;
format=flowed

Sorry for the crappy formatting, these answers are from a techie guy at=20=

the company in question. Apparently they have access to at least some=20=

of the source, at least enough to hook into it and add exporting=20
options. Oh, and I asked about recompiling to 32-bit, and the answer=20
was basically 'there's over 1,000,000 lines of code in this app. ain't=20=

gonna happen'. *shrug* It's their funeral...

When you say *connect VB4 to mysql* are you saying you want to export=20
your
accounting data from the VB4 app to the mysql database?

Yes.

In what format is the data stored at the moment?

Dbase Tables.

Does the app currently allow you to export the data? If so what formats=20=

are
available?

It does but we don=92t want to do several exports daily (Which would =
have=20
to be done from several different tables) via the built in export=20
function. We want the to modify the VB source code so that it directly=20=

conects to the mysql database and uploads the changed data daily.


--Apple-Mail-3-853089471--

Re: mysql with vb 4.0

--=_alternative 005A030985256FA4_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

RGF2aWQsIA0KDQpXaHkgYXJlIHlvdSB3b3JyaWVkIGFib3V0IGNvbm5lY3Rp bmcgeW91ciBWQjQg
Y29kZSB0byBNeVNRTD8gWW91IGFscmVhZHkgDQpzYWlkIHRoYXQgeW91IGFy ZSBzY3JhcHBpbmcg
dGhhdCBhcHBsaWNhdGlvbiBmb3IgYSBuZXcgaW50ZXJmYWNlIGJ1aWx0IG91 dCANCm9mIFBIUCwg
b3IgZGlkIEkgbWlzcmVhZCB0aGF0IGluIGFuIGVhcmxpZXIgbWVzc2FnZSBp biB0aGlzIHRocmVh
ZD8NCg0KTXkgb3BpbmlvbiBvbiBob3cgdGhpcyBzaG91bGQgcGxheSBvdXQu Li4gDQoNCiAgICAg
ICAgQSkgQmF0Y2ggY29udmVydCB5b3VyIGV4aXN0aW5nIGRhdGEgc28gdGhh dCB5b3UgaGF2ZSBh
IGNvcHkgb2YgaXQgDQppbiBNeVNRTCAoeW91IGRvbid0IG5lZWQgYSBWQjQg YXBwbGljYXRpb24g
dG8gZG8gdGhpcy4gQWxsIHlvdSBuZWVkIGlzIA0Kc29tZXRoaW5nIHRoYXQg Y2FuIHJlYWQgZnJv
bSBEQmFzZSBhbmQgd3JpdGUgdG8gTXlTUUwuKS4gDQoNCiAgICAgICAgQikg QnVpbGQgeW91ciBu
ZXcgUEhQIGFwcGxpY2F0aW9uIGFnYWluc3QgdGhpcyB0ZXN0IHNldCBvZiBk YXRhLiANCktlZXAg
eW91ciBjdXJyZW50IFZCNCBhY2NvdW50aW5nIGFwcCBvbmxpbmUuIA0KDQog ICAgICAgIEMpIFdo
ZW4geW91IGhhdmUgZmluaXNoZWQgdGVzdGluZyB5b3VyIFBIUCBhcHBsaWNh dGlvbiwgQ29udmVy
dCANCnlvdXIgY3VycmVudCBhY2NvdW50aW5nIGluZm9ybWF0aW9uIHRvIE15 U1FMICh5ZXMsIGRv
IGl0IGFnYWluLiBUaGlzIHRpbWUgDQp5b3VyIE15U1FMIGRhdGFiYXNlIHdp bGwgYmUgY29tcGxl
dGVseSB1cCB0byBkYXRlIHdpdGggdGhlIGxhdGVzdCBjaGFuZ2VzIA0KaW4g eW91ciBhY2NvdW50
cykuIFRlc3QgeW91ciBQSFAgYXBwbGljYXRpb24gaW4gcGFyYWxsZWwgd2l0 aCB5b3VyIA0KZXhp
c3Rpbmcgc3lzdGVtIGZvciBzb21lIHBlcmlvZCBvZiB0aW1lLiBNYWtlIHN1 cmUgdGhlcmUgaXMg
bm90aGluZyB0aGUgDQpuZXcgYXBwbGljYXRpb24gY2FuJ3QgZG8gdGhhdCB5 b3UgbmVlZCBpdCB0
byBkbyBhbmQgdGhhdCBpdCBpcyBrZWVwaW5nIA0KYWNjdXJhdGUgYm9va3Mu DQoNCiAgICAgICAg
RCkgSUYgdGVzdGluZyBpcyBnb29kIChib3RoIHNldHMgb2YgYm9va3MgYXJl IHN0aWxsIGluIHN5
bmMpIGFmdGVyIA0KeW91ciBtaXJyb3IgdGVzdGluZyBwaGFzZSBhbmQgYWxs IHJlbWFpbmluZyBi
dWdzIGFyZSB3b3JrZWQgb3V0LiBNYWtlIHRoZSANCmRlY2lzaW9uIHRvIHN0 b3AgdXNpbmcgeW91
ciBleGlzdGluZyBWQjQtYmFzZWQgYWNjb3VudGluZyBwYWNrYWdlIGFuZCB1 c2UgDQp5b3VyIFBI
UCBmcm9udCBlbmQgZXhjbHVzaXZlbHkuDQoNCklmIHlvdSBhcmUgbW92aW5n IGZyb20gb25lIGRl
YWQgYXBwIHRvIGEgbmV3IGZyb250IGVuZCwgd2h5IGFyZSB5b3UgDQp3b3Jy aWVkIGFib3V0IGxp
dmUgY29ubmVjdGl2aXR5Pw0KDQpTaGF3biBHcmVlbg0KRGF0YWJhc2UgQWRt aW5pc3RyYXRvcg0K
VW5pbWluIENvcnBvcmF0aW9uIC0gU3BydWNlIFBpbmUNCg0KRGF2aWQgQmlz aG9wIDx0ZWFuY29t
QGdtYWlsLmNvbT4gd3JvdGUgb24gMDIvMDkvMjAwNSAxMToyMTo0OCBQTToN Cg0KPiBTb3JyeSBm
b3IgdGhlIGNyYXBweSBmb3JtYXR0aW5nLCB0aGVzZSBhbnN3ZXJzIGFyZSBm cm9tIGEgdGVjaGll
IGd1eSBhdCANCj4gdGhlIGNvbXBhbnkgaW4gcXVlc3Rpb24uICBBcHBhcmVu dGx5IHRoZXkgaGF2
ZSBhY2Nlc3MgdG8gYXQgbGVhc3Qgc29tZSANCj4gb2YgdGhlIHNvdXJjZSwg YXQgbGVhc3QgZW5v
dWdoIHRvIGhvb2sgaW50byBpdCBhbmQgYWRkIGV4cG9ydGluZyANCj4gb3B0 aW9ucy4gIE9oLCBh
bmQgSSBhc2tlZCBhYm91dCByZWNvbXBpbGluZyB0byAzMi1iaXQsIGFuZCB0 aGUgYW5zd2VyIA0K
PiB3YXMgYmFzaWNhbGx5ICd0aGVyZSdzIG92ZXIgMSwwMDAsMDAwIGxpbmVz IG9mIGNvZGUgaW4g
dGhpcyBhcHAuICBhaW4ndCANCj4gZ29ubmEgaGFwcGVuJy4gICpzaHJ1Zyog IEl0J3MgdGhlaXIg
ZnVuZXJhbC4uLg0KPiANCj4gV2hlbiB5b3Ugc2F5ICpjb25uZWN0IFZCNCB0 byBteXNxbCogYXJl
IHlvdSBzYXlpbmcgeW91IHdhbnQgdG8gZXhwb3J0IA0KPiB5b3VyDQo+IGFj Y291bnRpbmcgZGF0
YSBmcm9tIHRoZSBWQjQgYXBwIHRvIHRoZSBteXNxbCBkYXRhYmFzZT8NCj4g DQo+IFllcy4NCj4g
DQo+IEluIHdoYXQgZm9ybWF0IGlzIHRoZSBkYXRhIHN0b3JlZCBhdCB0aGUg bW9tZW50Pw0KPiAN
Cj4gRGJhc2UgVGFibGVzLg0KPiANCj4gRG9lcyB0aGUgYXBwIGN1cnJlbnRs eSBhbGxvdyB5b3Ug
dG8gZXhwb3J0IHRoZSBkYXRhPyBJZiBzbyB3aGF0IGZvcm1hdHMgDQo+IGFy ZQ0KPiBhdmFpbGFi
bGU/DQo+IA0KPiBJdCBkb2VzIGJ1dCB3ZSBkb27igJl0IHdhbnQgdG8gZG8g c2V2ZXJhbCBleHBv
cnRzIGRhaWx5IChXaGljaCB3b3VsZCBoYXZlIA0KPiB0byBiZSBkb25lIGZy b20gc2V2ZXJhbCBk
aWZmZXJlbnQgdGFibGVzKSB2aWEgdGhlIGJ1aWx0IGluIGV4cG9ydCANCj4g ZnVuY3Rpb24uIFdl
IHdhbnQgdGhlIHRvIG1vZGlmeSB0aGUgVkIgc291cmNlIGNvZGUgc28gdGhh dCBpdCBkaXJlY3Rs
eSANCj4gY29uZWN0cyB0byB0aGUgbXlzcWwgZGF0YWJhc2UgYW5kIHVwbG9h ZHMgdGhlIGNoYW5n
ZWQgZGF0YSBkYWlseS4NCj4gDQoNCg==
--=_alternative 005A030985256FA4_=--

Re: mysql with vb 4.0

--Apple-Mail-1-936687565
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=WINDOWS-1252;
format=flowed


Either you misread it or I mis-typed it :-) The backend VB4 product=20
will be in use for the forseeable future, with a web-frontend store to=20=

tie into it. The VB4 app does *everything* product related for this=20
company - inventory, sales, etc - while the web is 'just' an online=20
store.

Hope that clears up any lingering confusion :-)

David

On Feb 10, 2005, at 9:20 AM, SGreen@unimin.com wrote:

>
> David,
>
> Why are you worried about connecting your VB4 code to MySQL? You=20
> already said that you are scrapping that application for a new=20
> interface built out of PHP, or did I misread that in an earlier=20
> message in this thread?
>
> My opinion on how this should play out...
>
> =A0 =A0 =A0 =A0 A) Batch convert your existing data so that you have a =
copy of=20
> it in MySQL (you don't need a VB4 application to do this. All you need=20=

> is something that can read from DBase and write to MySQL.).
>
> =A0 =A0 =A0 =A0 B) Build your new PHP application against this test =
set of=20
> data. Keep your current VB4 accounting app online.
>
> =A0 =A0 =A0 =A0 C) When you have finished testing your PHP =
application,=20
> Convert your current accounting information to MySQL (yes, do it=20
> again. This time your MySQL database will be completely up to date=20
> with the latest changes in your accounts). Test your PHP application=20=

> in parallel with your existing system for some period of time. Make=20
> sure there is nothing the new application can't do that you need it to=20=

> do and that it is keeping accurate books.
>
> =A0 =A0 =A0 =A0 D) IF testing is good (both sets of books are still in =
sync)=20
> after your mirror testing phase and all remaining bugs are worked out.=20=

> Make the decision to stop using your existing VB4-based accounting=20
> package and use your PHP front end exclusively.
>
> If you are moving from one dead app to a new front end, why are you=20
> worried about live connectivity?
>
> Shawn Green
> Database Administrator
> Unimin Corporation - Spruce Pine
>
> David Bishop wrote on 02/09/2005 11:21:48 PM:
>
> > Sorry for the crappy formatting, these answers are from a techie=20
> guy at
> > the company in question. =A0Apparently they have access to at least=20=

> some
> > of the source, at least enough to hook into it and add exporting
> > options. =A0Oh, and I asked about recompiling to 32-bit, and the=20
> answer
> > was basically 'there's over 1,000,000 lines of code in this app.=20
> =A0ain't
> > gonna happen'. =A0*shrug* =A0It's their funeral...
> >
> > When you say *connect VB4 to mysql* are you saying you want to=20
> export
> > your
> > accounting data from the VB4 app to the mysql database?
> >
> > Yes.
> >
> > In what format is the data stored at the moment?
> >
> > Dbase Tables.
> >
> > Does the app currently allow you to export the data? If so what=20
> formats
> > are
> > available?
> >
> > It does but we don=92t want to do several exports daily (Which =
would=20
> have
> > to be done from several different tables) via the built in export
> > function. We want the to modify the VB source code so that it=20
> directly
> > conects to the mysql database and uploads the changed data daily.
> >

--Apple-Mail-1-936687565--

Re: mysql with vb 4.0

Ok, I'll keep my previous statement, I think you won't be able to
export the changes everytime something is updated using the VB4 app,
because that is surely a built-in function unavailable to you, and the
company that made the software will think twice before changing every
line of code that does an update to add conectivity to a MySQL DB, it
will slow down the operation a bit (writting in both DBs), and it will
certainly drive the coder nuts if the app indeed have that many lines
of code.

Your best option in my opinnion is to link the web code directly with
the DB that's being used by the VB4 app (DBase), using PHP or any CGI
language, this way you skip conversions and have the updated DB
available every time. Get a driver for PHP capable of dealing with
DBase, you're done.

It's just my two cents, but I really think that except for the
language you choose and the web interface, you don't have much choice
on how to do this...

Best regards,

--
Daniel da Veiga
Computer Operator - RS - Brazil

--
MySQL Windows Mailing List
For list archives: http://lists.mysql.com/win32
To unsubscribe: http://lists.mysql.com/win32?unsub=gcdmw-win32@m.gmane.org

Re: mysql with vb 4.0

--=_alternative 004FC19F85256FA5_=
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

RGF2aWQgQmlzaG9wIDx0ZWFuY29tQGdtYWlsLmNvbT4gd3JvdGUgb24gMDIv MTAvMjAwNSAxMDoz
NTowNiBQTToNCg0KPiANCj4gRWl0aGVyIHlvdSBtaXNyZWFkIGl0IG9yIEkg bWlzLXR5cGVkIGl0
IDotKSAgVGhlIGJhY2tlbmQgVkI0IHByb2R1Y3QgDQo+IHdpbGwgYmUgaW4g dXNlIGZvciB0aGUg
Zm9yc2VlYWJsZSBmdXR1cmUsIHdpdGggYSB3ZWItZnJvbnRlbmQgc3RvcmUg dG8gDQo+IHRpZSBp
bnRvIGl0LiAgVGhlIFZCNCBhcHAgZG9lcyAqZXZlcnl0aGluZyogcHJvZHVj dCByZWxhdGVkIGZv
ciB0aGlzIA0KPiBjb21wYW55IC0gaW52ZW50b3J5LCBzYWxlcywgZXRjIC0g d2hpbGUgdGhlIHdl
YiBpcyAnanVzdCcgYW4gb25saW5lIA0KPiBzdG9yZS4NCj4gDQo+IEhvcGUg dGhhdCBjbGVhcnMg
dXAgYW55IGxpbmdlcmluZyBjb25mdXNpb24gOi0pDQo+IA0KPiBEYXZpZA0K DQoNClllcywgaXQg
bWFrZXMgeW91ciBjaG9pY2UgYWNhZGVtaWMuIFlvdXIgUEhQIGZyb250IGVu ZCBoYXMgdG8gd29y
ayB3aXRoIA0KdGhlIERCYXNlIGJhY2tlbmQuIFRvIGRvIG90aGVyd2lzZSB3 b3VsZCBtYWtlIHlv
dXIgc2l0dWF0aW9uIGludG8gYSANCm1haW50ZW5hbmNlIG5pZ2h0bWFyZS4g SSB3b3VsZCBhbHNv
IHRha2UgYSBsb25nIGhhcmQgbG9vayBhdCB0aGUgYW5hbHlzaXMgDQpza2ls bHMgb2YgdGhlIHBl
cnNvbiB3aG8gc3VnZ2VzdGVkIE15U1FMIHRvIHlvdSBpbiB0aGUgZmlyc3Qg cGxhY2UuIElmIA0K
dGhleSBoYWQgdHJ1bHkgdW5kZXJzdG9vZCB0aGF0IHlvdSB3ZXJlIG5vdCBn b2luZyB0byByZXBs
YWNlIHlvdXIgVkI0IGFwcCANCmFuZCB0aGF0IGl0IHdhcyBub3QgZ29pbmcg dG8gYmUgbW9kaWZp
ZWQgdG8gd29yayB3aXRoIE15U1FMIChiZWNhdXNlIGl0J3MgDQphIHByb3By aWV0YXJ5IGFwcGxp
Y2F0aW9uKSB0aGVuIHRoZXkgc2hvdWxkIGhhdmUgc2VlbiB0aGF0IHRoZSBQ SFAtYmFzZWQgDQpz
dG9yZSBtdXN0IGhvb2sgaW50byB0aGUgREJhc2UgYmFja2VuZC4gU29tZWJv ZHkgbWFkZSBhIHBv
b3IgZGVzaWduIGNob2ljZSANCmFuZCBpdCB3YXMgZ29vZCB0aGF0IHdlIGNh dWdodCBpdCBub3cg
YW5kIG5vdCBsYXRlci4NCg0KSG93ZXZlciwgaWYgeW91IGV2ZXIgZGVjaWRl IHRvIHVzZSBNeVNR
TCBmb3Igb3RoZXIgcHVycG9zZXMsIHdlICh0aGUgDQptZW1iZXJzIG9mIHRo ZSBsaXN0KSBhcmUg
YWx3YXlzIGhlcmUgYW5kIGdsYWQgdG8gaGVscC4gQ29tZSBiYWNrIGlmIHlv dSANCm5lZWQgdXMg
Zm9yIGFueXRoaW5nISENCg0KU2hhd24gR3JlZW4NCkRhdGFiYXNlIEFkbWlu aXN0cmF0b3INClVu
aW1pbiBDb3Jwb3JhdGlvbiAtIFNwcnVjZSBQaW5lDQoNCg0KDQoNCj4gT24g RmViIDEwLCAyMDA1
LCBhdCA5OjIwIEFNLCBTR3JlZW5AdW5pbWluLmNvbSB3cm90ZToNCj4gDQo+ ID4NCj4gPiBEYXZp
ZCwNCj4gPg0KPiA+IFdoeSBhcmUgeW91IHdvcnJpZWQgYWJvdXQgY29ubmVj dGluZyB5b3VyIFZC
NCBjb2RlIHRvIE15U1FMPyBZb3UgDQo+ID4gYWxyZWFkeSBzYWlkIHRoYXQg eW91IGFyZSBzY3Jh
cHBpbmcgdGhhdCBhcHBsaWNhdGlvbiBmb3IgYSBuZXcgDQo+ID4gaW50ZXJm YWNlIGJ1aWx0IG91
dCBvZiBQSFAsIG9yIGRpZCBJIG1pc3JlYWQgdGhhdCBpbiBhbiBlYXJsaWVy IA0KPiA+IG1lc3Nh
Z2UgaW4gdGhpcyB0aHJlYWQ/DQo+ID4NCj4gPiBNeSBvcGluaW9uIG9uIGhv dyB0aGlzIHNob3Vs
ZCBwbGF5IG91dC4uLg0KPiA+DQo+ID4gICAgICAgICBBKSBCYXRjaCBjb252 ZXJ0IHlvdXIgZXhp
c3RpbmcgZGF0YSBzbyB0aGF0IHlvdSBoYXZlIGEgY29weSBvZiANCg0KPiA+ IGl0IGluIE15U1FM
ICh5b3UgZG9uJ3QgbmVlZCBhIFZCNCBhcHBsaWNhdGlvbiB0byBkbyB0aGlz LiBBbGwgeW91IG5l
ZWQgDQoNCj4gPiBpcyBzb21ldGhpbmcgdGhhdCBjYW4gcmVhZCBmcm9tIERC YXNlIGFuZCB3cml0
ZSB0byBNeVNRTC4pLg0KPiA+DQo+ID4gICAgICAgICBCKSBCdWlsZCB5b3Vy IG5ldyBQSFAgYXBw
bGljYXRpb24gYWdhaW5zdCB0aGlzIHRlc3Qgc2V0IG9mIA0KPiA+IGRhdGEu IEtlZXAgeW91ciBj
dXJyZW50IFZCNCBhY2NvdW50aW5nIGFwcCBvbmxpbmUuDQo+ID4NCj4gPiAg ICAgICAgIEMpIFdo
ZW4geW91IGhhdmUgZmluaXNoZWQgdGVzdGluZyB5b3VyIFBIUCBhcHBsaWNh dGlvbiwgDQo+ID4g
Q29udmVydCB5b3VyIGN1cnJlbnQgYWNjb3VudGluZyBpbmZvcm1hdGlvbiB0 byBNeVNRTCAoeWVz
LCBkbyBpdCANCj4gPiBhZ2Fpbi4gVGhpcyB0aW1lIHlvdXIgTXlTUUwgZGF0 YWJhc2Ugd2lsbCBi
ZSBjb21wbGV0ZWx5IHVwIHRvIGRhdGUgDQo+ID4gd2l0aCB0aGUgbGF0ZXN0 IGNoYW5nZXMgaW4g
eW91ciBhY2NvdW50cykuIFRlc3QgeW91ciBQSFAgYXBwbGljYXRpb24gDQo+ ID4gaW4gcGFyYWxs
ZWwgd2l0aCB5b3VyIGV4aXN0aW5nIHN5c3RlbSBmb3Igc29tZSBwZXJpb2Qg b2YgdGltZS4gTWFr
ZSANCj4gPiBzdXJlIHRoZXJlIGlzIG5vdGhpbmcgdGhlIG5ldyBhcHBsaWNh dGlvbiBjYW4ndCBk
byB0aGF0IHlvdSBuZWVkIGl0IHRvIA0KDQo+ID4gZG8gYW5kIHRoYXQgaXQg aXMga2VlcGluZyBh
Y2N1cmF0ZSBib29rcy4NCj4gPg0KPiA+ICAgICAgICAgRCkgSUYgdGVzdGlu ZyBpcyBnb29kIChi
b3RoIHNldHMgb2YgYm9va3MgYXJlIHN0aWxsIGluIHN5bmMpIA0KPiA+IGFm dGVyIHlvdXIgbWly
cm9yIHRlc3RpbmcgcGhhc2UgYW5kIGFsbCByZW1haW5pbmcgYnVncyBhcmUg d29ya2VkIG91dC4g
DQoNCj4gPiBNYWtlIHRoZSBkZWNpc2lvbiB0byBzdG9wIHVzaW5nIHlvdXIg ZXhpc3RpbmcgVkI0
LWJhc2VkIGFjY291bnRpbmcgDQo+ID4gcGFja2FnZSBhbmQgdXNlIHlvdXIg UEhQIGZyb250IGVu
ZCBleGNsdXNpdmVseS4NCj4gPg0KPiA+IElmIHlvdSBhcmUgbW92aW5nIGZy b20gb25lIGRlYWQg
YXBwIHRvIGEgbmV3IGZyb250IGVuZCwgd2h5IGFyZSB5b3UgDQo+ID4gd29y cmllZCBhYm91dCBs
aXZlIGNvbm5lY3Rpdml0eT8NCj4gPg0KPiA+IFNoYXduIEdyZWVuDQo+ID4g IERhdGFiYXNlIEFk
bWluaXN0cmF0b3INCj4gPiAgVW5pbWluIENvcnBvcmF0aW9uIC0gU3BydWNl IFBpbmUNCj4gPg0K
PiA+IERhdmlkIEJpc2hvcCA8dGVhbmNvbUBnbWFpbC5jb20+IHdyb3RlIG9u IDAyLzA5LzIwMDUg
MTE6MjE6NDggUE06DQo+ID4NCj4gPiAgPiBTb3JyeSBmb3IgdGhlIGNyYXBw eSBmb3JtYXR0aW5n
LCB0aGVzZSBhbnN3ZXJzIGFyZSBmcm9tIGEgdGVjaGllIA0KPiA+IGd1eSBh dA0KPiA+ICA+IHRo
ZSBjb21wYW55IGluIHF1ZXN0aW9uLiAgQXBwYXJlbnRseSB0aGV5IGhhdmUg YWNjZXNzIHRvIGF0
IGxlYXN0IA0KPiA+IHNvbWUNCj4gPiAgPiBvZiB0aGUgc291cmNlLCBhdCBs ZWFzdCBlbm91Z2gg
dG8gaG9vayBpbnRvIGl0IGFuZCBhZGQgZXhwb3J0aW5nDQo+ID4gID4gb3B0 aW9ucy4gIE9oLCBh
bmQgSSBhc2tlZCBhYm91dCByZWNvbXBpbGluZyB0byAzMi1iaXQsIGFuZCB0 aGUgDQo+ID4gYW5z
d2VyDQo+ID4gID4gd2FzIGJhc2ljYWxseSAndGhlcmUncyBvdmVyIDEsMDAw LDAwMCBsaW5lcyBv
ZiBjb2RlIGluIHRoaXMgYXBwLiANCj4gPiAgYWluJ3QNCj4gPiAgPiBnb25u YSBoYXBwZW4nLiAg
KnNocnVnKiAgSXQncyB0aGVpciBmdW5lcmFsLi4uDQo+ID4gID4NCj4gPiAg PiBXaGVuIHlvdSBz
YXkgKmNvbm5lY3QgVkI0IHRvIG15c3FsKiBhcmUgeW91IHNheWluZyB5b3Ug d2FudCB0byANCj4g
PiBleHBvcnQNCj4gPiAgPiB5b3VyDQo+ID4gID4gYWNjb3VudGluZyBkYXRh IGZyb20gdGhlIFZC
NCBhcHAgdG8gdGhlIG15c3FsIGRhdGFiYXNlPw0KPiA+ICA+DQo+ID4gID4g WWVzLg0KPiA+ICA+
DQo+ID4gID4gSW4gd2hhdCBmb3JtYXQgaXMgdGhlIGRhdGEgc3RvcmVkIGF0 IHRoZSBtb21lbnQ/
DQo+ID4gID4NCj4gPiAgPiBEYmFzZSBUYWJsZXMuDQo+ID4gID4NCj4gPiAg PiBEb2VzIHRoZSBh
cHAgY3VycmVudGx5IGFsbG93IHlvdSB0byBleHBvcnQgdGhlIGRhdGE/IElm IHNvIHdoYXQgDQo+
ID4gZm9ybWF0cw0KPiA+ICA+IGFyZQ0KPiA+ICA+IGF2YWlsYWJsZT8NCj4g PiAgPg0KPiA+ICA+
IEl0IGRvZXMgYnV0IHdlIGRvbuKAmXQgd2FudCB0byBkbyBzZXZlcmFsIGV4 cG9ydHMgZGFpbHkg
KFdoaWNoIHdvdWxkIA0KPiA+IGhhdmUNCj4gPiAgPiB0byBiZSBkb25lIGZy b20gc2V2ZXJhbCBk
aWZmZXJlbnQgdGFibGVzKSB2aWEgdGhlIGJ1aWx0IGluIGV4cG9ydA0KPiA+ ICA+IGZ1bmN0aW9u
LiBXZSB3YW50IHRoZSB0byBtb2RpZnkgdGhlIFZCIHNvdXJjZSBjb2RlIHNv IHRoYXQgaXQgDQo+
ID4gZGlyZWN0bHkNCj4gPiAgPiBjb25lY3RzIHRvIHRoZSBteXNxbCBkYXRh YmFzZSBhbmQgdXBs
b2FkcyB0aGUgY2hhbmdlZCBkYXRhIGRhaWx5Lg0KPiA+ICA+DQoNCg==
--=_alternative 004FC19F85256FA5_=--