Any suggestions,
Thanks,
Ryan
Truly sickening.
Because VID does have some neat tools but only if you can get as far
as to be able to use them.
Even if you get past the stupid connection to server, you will run
into the next big problem " Cannot start debugger on the server"
What fucking good is the VId if you cannot run debugger ?
My suggestion :- > Return VID to Bill Gates and get your money back
and use a freeware editor like Aracnaphila or something.
Don't waste your time with VID because even if you get it working ,
you will run into the same on another PC.
I searched the web for these errors (Yahoo has some links to Microsoft
KB) and went thru all the crap but no luck (extensions and all that
bullshit). Studio has been around for more than 3 years and one woudl
think they would fix these basic issues.
Disgusting
IIS is another piece of crap & I don't even want to go there
<ros...@prodigy.net> wrote in message
news:3bc0e2cc...@news.prodigy.net...
If you're IIS is version 4, the IIS server OS is NT4sp6 and your VI
development machine is NT4 sp3 they will not connect. Just hang.
Check the event logs.
It would help to manage the configuration and report or have a link to
a report that gives your configurations in detail. There are lots of
significant details: service pack/version of: IIS, VS6, OS, dabase
manager/server, project mode local or master are some that immediately
come to mind. Also what kind of security was chosen for the SQL
Server, etc. etc.
Lets start with these (or discuss soem other "better" config.
description) else we are probably just wasting time...assuming VI is
not already dead!