Of course you can drag and drop to an existing class library. If one does not exist, just create a class library with something you can delete later.

After you do that, you might have problems still. Usually with the referencing of the class library. You can check this by opening the class library like a table. e.g. Use blah.vcx

Browse the vcx and look at the classloc memo field. Make sure that the location of the library is pointing to the appropriate parent class library.


Personally, I have just put all of my classes into a single VCX file. If I really wanted to separate them out then I would do it based on the "baseclass".

All text boxes into a single class. All labels into another class. All combo boxes into another class. Separating them from their parents makes it difficult to keep track of.

I personally have four class libraries.
1. Generic objects that can be applied to any application
2. Application or customer specific
3. MSINET ActiveX object which is layered for FTP processing. Also programmed for doing duplicate calls with a single connection. E.g. something Microsoft says can't be done with their INET stuff. I will explain later.
4. Other ActiveX objects


In reference to 3:

Micrsoft states that a call to a FTP server requires multiple calls.
1. Open connection
2. Execute statement
3. Close connection
4. open Connection
5. Second statement
6. Close connection

I have created a work around, which allows for multiple commands in the same connection space. It involves a timer and a call to "BOOT" the process into working. The boot simple calls the StateChanged method with a 12.

What were we talking about again... :-)