Suggestion on architecture please

I have an ActiveX .dll created in VB6 that we are converting to .NET. We are investigating moveing to web services. So...
Should we re-create the .dll as a class library, then tie a web service to it and expose the class functions and properties, or should the complete dll be converted to a web service with functions and properties exposed. There is about 4000 lines of code with various properties and ODBC links to MS-SQL7 in the VB6 version.
I tried to rationalize either fashion through MSDN how to's etc... but can't seem to find an answer. Your suggestions and/or experiences would be appreciated.
Thanks

Depends... if it's strictly going to be called thru the web, then the webservice is just fine. If it could also be used in non-web environment, then I'd create a normal DLL and then another interface to provice the webservice functionality. (Actually, I'd probably do the later regardless)... just my opinion.

It's going to take roughly the same amount of time to do either conversion/re-write. Like DSJ said, the later would allow you to re-use this code in a non-web environment, which it sounds like you are doing now.

Quote:

---

Actually, I'd probably do the later regardless

---

Yep, thats the route we're going to try.
Thanks for the postback guys!