Design time Controls

Re: The lack of response

Came to the same conclusion myself. have now junked the DTCs and re written the code.
cheers Karl

The lack of response

The response you are getting shows how unloved DTC in Visual interDev really are.

They are buggy, difficult to customise and obsolete now with ASP.NET.

My advice is to ditch the aborted M$ technology ASAP.

e.g. www.zdnet.com.au/builder/architect/sdi/story/0,2000035062,20267211,00.htm

and a review of InterDev:

Visual InterDev's DTC's (design times controls) have many bugs and documentation errors. Examples cut and pasted directly from the documentation generate syntax errors. If you create a page with too many DTC's it takes forever for Visual InterDev to render the code. The code it does generate is incredibly bloated and is difficult to modify. I doubt a site created with DTCs could handle very much traffic. The underlying FrontPage Editor that it uses for graphical page editing is the very tired 97 version. It is handy as an ASP text editor but is overpriced if that is it's only function. Of course the product has been made competely obsolete by .NET.

I have built sites in the past with them and I hated the whole experience. As did the users who wanted flexibility.

I know it doesn't answer your question, but boy, do DTC suck.:x

Have used DTC's to build some web pages using Visual studio 6 / interdeve. The web site works on the local server w2k + iis. Have published to web server on my virtual host but the pages do not work. I have modified the globala.asa to point the data connections to the server and have checked that the server is running frontpage extensions as required.
Normal asp pages running direct connection to the db work.
Anything I am missing here ?