[AccessD] Learning .Net -- PHP Instead?

Hmmm, I don't really have a 'test' project anymore, at least none that I
could find.  There's several steps involved.  If this is something you
are really interested in (I've only used it a few times), I could send
you something  I built that uses this. 

It's a program I don't use anymore, that would update a site with
pictures it downloaded from another site.  These 'pictures' (and some
data) were downloaded as zip files.  Once a file was downloaded, it
would launch an unzip routine, in another thread, while it began to
download the other files.  Worked pretty well, the downloading was never
interrupted by the unzip processes, so when the downloading was
complete, usually it just had to wait for the last unzip, before it
would continue the process of updating the site and database.  The fun
part of multi-threading in VB6 like this (keep in mind, you can't do
this with VBA), is communicating between threads.  Lots of API calls.
But if you'd like to take a look at that particular program let me know,
and I'll send it to you offlist.

Drew

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim Lawrence
Sent: Thursday, June 25, 2009 12:16 AM
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Learning .Net -- PHP Instead?

Hi Drew:

You should post the code... that would be very informative. 8-)

Jim 

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka
Sent: Wednesday, June 24, 2009 3:06 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Learning .Net -- PHP Instead?

It is!  You can multithread in VB 6, though it's compartmented (sorry,
long day, I might have the terminology wrong).  It will run two distinct
thread ID's, and the processes will run completely separate.  (One can
error out, and stop, and the others will keep going).  One funny thing I
noticed back when I played around with that, is that in testing, I ran a
database dump, where my routine was dumping dummy data into a table.
Running against a 97 .mdb, it would eventually crash, due to a writing
clash (because since the code was running in separate threads, the OS,
not the program, was handling which process got to do what first..., so
two 'writes' at the exact same time could clash), and I would end up
with a  corrupted database.  Didn't have that problem with a 2000
database, left it running until it filled the database, never crashed.
Who'da thunk that a 2000 mdb would be more stable then a 97 mdb in any
aspect! ;)

Drew

The information contained in this transmission is intended only for the person or entity 
to which it is addressed and may contain II-VI Proprietary and/or II-VI Business 
Sensitive material. If you are not the intended recipient, please contact the sender 
immediately and destroy the material in its entirety, whether electronic or hard copy. 
You are notified that any review, retransmission, copying, disclosure, dissemination, 
or other use of, or taking of any action in reliance upon this information by persons 
or entities other than the intended recipient is prohibited.