> If you instead choose to go the web-app way (I would), rewrite the
> client-app as asp web-pages instead. If your existing client-app
> have its business-logic separated into ActiveX dlls already, the
> asp-pages can use it directly.
I would too, or, if you use .Net (can you say that here?), you can write it as a
web service. This lets you put most of the app on the server under ASP, just as
with a web app, while still having all the bells and whistles of a client
windows app (smoother grids, local data caching, etc). Big install required, but
for in-house deployment, thats pretty easy to do. The results, I must say, are
quite impressive, even if it is MS and .Net and bloated and all that.
Dag Sunde - 30 Aug 2006 04:17 GMT
>> If you instead choose to go the web-app way (I would), rewrite the
>> client-app as asp web-pages instead. If your existing client-app
[quoted text clipped - 8 lines]
> deployment, thats pretty easy to do. The results, I must say, are
> quite impressive, even if it is MS and .Net and bloated and all that.
That is also a good idea!
I'll just have to add that you don't need .NET to write all the business
logic as web services. I have written several in VB6.
If you have the core buisiness logic as activeX dlls, it's just a matter
of running a Wizard on them to pick the menthods you want to expose as
web-services...

Signature
Dag.
Steve Gerrard - 30 Aug 2006 04:30 GMT
> I'll just have to add that you don't need .NET to write all the business
> logic as web services. I have written several in VB6.
>
> If you have the core buisiness logic as activeX dlls, it's just a matter
> of running a Wizard on them to pick the menthods you want to expose as
> web-services...
I agree on the server side, but I am not aware of an easy way to use web
services for data in a VB6 client. Using one in a .Net windows client is quite
easy. That's where the big install comes in, though.
Dag Sunde - 30 Aug 2006 10:40 GMT
>> I'll just have to add that you don't need .NET to write all the
>> business logic as web services. I have written several in VB6.
[quoted text clipped - 6 lines]
> web services for data in a VB6 client. Using one in a .Net windows
> client is quite easy. That's where the big install comes in, though.
Complex data-structures like classes are a PITA to marshall in VB6,
even with the WSDL file, but discrete datatypes like String, Long,
Byte, Boolean, et.c is pretty straightforward.
you just add a reference to Microsoft SOAP Type Library (MSSOAP1.dll)
to your project, and put this in your code:
Dim oSOAPClient As SoapClient
Set oSOAPClient = New SoapClient
oSOAPClient.mssoapinit _
"http://www.dagsunde.com/soap/urn:dagsunde-quotes.wsdl"
MsgBox objSOAPClient.getQuote("IBM")

Signature
Dag.
Steve Gerrard - 30 Aug 2006 15:51 GMT
>> I agree on the server side, but I am not aware of an easy way to use
>> web services for data in a VB6 client. Using one in a .Net windows
[quoted text clipped - 14 lines]
>
> MsgBox objSOAPClient.getQuote("IBM")
Thanks for the sample, Dag, I will try some things out. There are some places
where some simple data transfers would be useful.
The big attraction of a .Net client to me was being able to pass an entire data
set in one call - a project record, with maybe a dozen related detail records.
The client can then mess around on their own, updating several records at once,
and save by sending the whole data set back at once.