Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Search results for query: *

  1. dareseka

    ASP.NET Web Controls not visible on Client

    DaZZleD (!), thanks for responding I agree that these things shouldn't have to be installed on the client; those things were installed as part of my trouble-shooting process (again, I'm a newbee at web development). The controls that aren't visible from the client are all Web Forms controls...
  2. dareseka

    ASP.NET Web Controls not visible on Client

    I'VE HAD IT!!! I'm a VB (6-.NET) programmer trying my hand at ASP.NET and I've been dealing with this same problem for days. Here it is: I've created a number of aspx files with server controls; everything look fine on my pc, but when I try and access the pages from another client workstation...
  3. dareseka

    AS/400 Netserver QZLSSERVER can not start - reason code 6

    Please help! We've been receiving the following error when our AS/400 IPL's: 'The required AS/400 NetServer job QZLSSERVER wa unable to start because of reason code 6.' Reason Code 6 = Start of the internal server failed with return code 3409. Apparently, there is a problem when the system...
  4. dareseka

    Compiled on XP, Installed on NT

    THANKS for the suggestion... and the QUICK RESPONSE! I'm going to give it a try. I'll let you know if it works for me too. [thumbsup2]
  5. dareseka

    Compiled on XP, Installed on NT

    Maybe someone can help me 'undo' what I've 'done'. I've created a VB6 application and compiled it in Windows XP. The application was installed on a number stations with different platforms, including Windows NT 4.0. Usually you don't have many compatibility issues when installing newer...

Part and Inventory Search

Back
Top