Hi Steve,
Thanks, the python versions I had read up on when finally finding the
correct PyInstaller version, 2.0, for it uses those versions and stores them
where needed when compiling. I was having issues when using 2.5 or 2.7 version
of Python but once I found the correct PyInstaller versi
Bruce,
FYI, python 2.5 was built against the 2005 runtime, 2.6 and 2.7 were
built with 2008, and 3.x is built against 2010.
However, if you're concerned with operations blocking or impairing the
responsiveness of your app, then you'll likely want to put your typical
GUI-handling event handle
Hi Steve and Rick,
Just got home and read all the comments and yes Steve you have to be
careful for as I had stated, studio changed that run time dll each new version
they came out with. The original Python one only uses the MSVCRT with no
number, but as both progressed, into Python 2.6 and
Thanks for that excellant overview Steve.
He is getting deeper than I go in my usual VB.net / DB programming.
I avoided C++ for those reasons, hay, why ReInvent the wheel.
Later and that really was a nice abstract.
Rick USA
Greetings,
Just to minimize any misunderstanding concerning the C runtime, I think
the following page might help:
http://stackoverflow.com/questions/2766233/what-is-the-c-runtime-library. Note,
in essence, that this is a set of components needed for C or C++-based
applications to communicate
Hi Again Bruce: OK, I reviewed the MSCRT dll and found out what it all means
and understand what you are trying to do.
I am not sure you can hook into the MSCRT dll from within a VBScript in any
case but I could be wrong.
There seems to be allot going on in the Visual C Library which may require
Hi Bruce: I am not familiar with most of those technicals but will blast
through google to get a flavor for what you are using.
To add a dll to a vb.net project you copy the dll into a folder, I usually put
them in the same folder as the executable I am going to distribute. Then in the
vb.net ID
