Subj : Re: DLL Entry point missing To : borland.public.cpp.borlandcpp From : "Ed Mulroy [TeamB]" Date : Sat Jan 24 2004 03:16 pm > The window that apeared is attached as a image (failed...) As you can see in the newsgroup guidelines, attachments are banned here: http://info.borland.com/newsgroups/guide.html If you must post an attachment, there is a group for that: borland.public.attachments My reply was because I did not see in what you showed anything which appeared to be related to something of a type or style which would require registration and no classes let alone OWL items. It has been years since I did any OLE stuff with BC++ (the last BC++ version, 5.02, is from 7 years ago). I remember needing to automate one or more classes in ClassExpert and that would also cause TApplication to be exposed. While your DllEntryPoint looks correct I remember OwlMain as the entry point although that is the name used in a OWL EXE so is probably wrong. If none of this is helpful then it would probably be best for you to post a new message with your question as others will see that I've replied and think the question had been handled. .. Ed > Bob van der Putten en Janetta Top wrote in message > news:401296e3$1@newsgroups.borland.com... > > Thanks for your reply, however it did not solve my problem > I want to regegister de DLL to be used in a ASP file by > CreateObject(...). So I wrote my DLL, and called Register > OLE Server command (right mouse click on project file, > and Special->Register OLE Server). Now I still get the > error. The window that apeared is attached as a image (failed...) > > It says: > ------------------------------------- > | Module entry point missing X | > ------------------------------------- > | DllRegisterCommand | > | | > | OK | > ------------------------------------- > > (Or don't I simply know what I'am doing....) .