I haven't been reading the entire thread so I apologize if this is an 
invalid response, but if it was me, I would definitely utilize the 
web to do this, although I'm not sure what I'm suggesting qualifies 
as a "web service" or not. I would either have the app pass all the 
data via a long URL with named parameters as your data, or do a 
direct http connection (west wind tools are great for this) and add 
post information for each data item). Both are really two different 
ways to do the same thing, although using the http connection route, 
you could read the returned html value and have some kind of embedded 
success or failure msg.

The interesting part of this idea, and perhaps where your question 
was already headed, is implementing the web server side to handle 
this. Personally I see no reason why VFP utilizing West Wind or other 
tool couldn't handle the request with ease. Not necessarily as a "web 
service" aka as defined by using SOAP, but as a regular web server 
application, like any normal html generating application. The 
difference here, is the server doesn't need to return any html 
output, it just handles the request, and inserts the mysql record 
with the metric data.

Additionally, it would also be fairly trivial to implement the server 
functionality in php, or any other web based development tool. It's 
not much code to simply read off parameters of the url and insert a 
record into mysql. So I guess I'm saying I don't see why you'd ever 
want to do this in dotnet unless you like dotnet. If it was me, I'd 
go the vfp route if your hosting the web server, and php route if not.

HTH -
Steve


>Rick,
>
>We want to create a functionality in our Sylvan app whereby the users
>would start-up the application and we simply want to capture their login
>metrics (userid, workstation name, version of software, date/time stamp).
>I had done this previously with SPT (SQLSTRINGCONNECT/SQLEXEC) to a MySQL
>database on the web.  Recent conversations had said (per PKM) that a web
>service would be better this time around since it could get through
>firewalls moreso.  Since this is a VFP9 app, what, iyo, would be the
>easiest/best way to design this?  My coworker has said VFP web service,
>but your comments above make me wonder (along with Allen's repeated
>problems it seems with VFP web services) if we'd be better off to use
>DotNet for this?
>
>tia,
>--Michael
>
>
>--
>Michael J. Babcock, MCP
>MB Software Solutions, LLC
>http://mbsoftwaresolutions.com
>http://fabmate.com
>"Work smarter, not harder, with MBSS custom software solutions!"
>
>
>
>
>
[excessive quoting removed by server]

_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
Searchable Archive: http://leafe.com/archives/search/profox
This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED]
** All postings, unless explicitly stated otherwise, are the opinions of the 
author, and do not constitute legal or medical advice. This statement is added 
to the messages for those lawyers who are too stupid to see the obvious.

Reply via email to