Any thoughts? Can it be done? Should it be done? Adverse affects?
All comments are appreciated.
|
|
|
Any thoughts? Can it be done? Should it be done? Adverse affects?
All comments are appreciated.
You will need separate DVB files for each OS. Otherwise the 32-bit DVB files, loaded in the 64-bit OS, will update references and attempt to make you save the changes.
Not to mention the performance issue.
Not to mention the fatal crash that will eventually "infect" you when you attempt to load code during S::Startup. (You don't start out that way, but eventually it happens.)
It is time to move to .NET.
R. Robert Bell
Design Technology Manager
Stantec
Opinions expressed are mine alone and do not reflect the views of Stantec.
At some point, not immediately, attempts to load VBA code using Visual LISP or even the VBALoad command, during the time S::Startup is running, will cause AutoCAD 2010 to fatally crash. So if your S::Startup function is using (vla-LoadDVB) or (command "._VBALoad") you run the risk of developing the fatal crash. Once you get the fatal crash, you will have it until you wipe and reinstall the OS.
http://forums.augi.com/showthread.php?t=52913 for starters.
R. Robert Bell
Design Technology Manager
Stantec
Opinions expressed are mine alone and do not reflect the views of Stantec.
OK, yea I reviewed all my startup lisp files and I don't have and DVB calls. I have stayed away from that because I don't like mixing apples and oranges.
It doesn't seem like my code is so complex as to cause issues. BUT, I will begin the transfer...
VB.NET... Lovely!
Thanks for the help