Judith -
A web service can be good if you need something instant to be updated in a
production database.
But - I'm guessing you DON'T need instantaneous updates.
With that in mind -
You can post the new records for your product tables onto the web server
via ftp at a windows workstation into the linux server as a diff file,
then have a process on the web server update the diff files.
Re: tracking which products were inquired about -
make a seperate table, 1 to many (back to the product table)
that only holds - productSKU, IP address of the requestor, other data you
need.
Then have a cron job run every night (on the linux server) to generate the
daily request files.
Then go pick up your files in the morning at a windows workstation via ftp
(or make another Task Scheduler Job somewhere).
I don't think you want to add in another WebServer running IIS at this
point - if your timings are not critical - ie - instantaneous - its not
needed.
Data file format, you ask ? All dbf files, using the fox2x file format.
Why Fox2X ? all php libraries can read and write dbf files, and Fox2x
matches that spec.
On to some of your other comments -
1. 'Basically the web service would allow remote users to query the
database for info about a certain product in the database'
If they are using a browser ONLY, you don't need a web service.
If they are using SOMETHING ELSE to query the database - WHAT ARE THEY USING?
2. 'My main objective is for the web service to be able to access the
data in my VFP database without my having to save the data in a different
database.'
IS a FREETABLE suffient, or are you really utilizing the VFP DBC ?
Also, can you live with different instances of your VFP database being in
two seperate places, on two Different Operating Systems?
3. ' I would also like to capture the product # in the request. '
If you want that for tracking purposes, then you want a two-way web
service. Maybe. Maybe not. If this really isn't a webservice, you can
capture a lot of stuff about the user making the request from the http
info.
----
The last time you put out some queries about your app, I had suggested
that you engage a consultant who knows about this stuff. I suggest now
you do the same thing -- engage a consultant who knows about this stuff. I
get the feeling (so far) that you haven't posted enough info for anyone to
give you a definative answer, but you're getting lots of options (even
from me) based on inadequate information. If your business processes are
proprietary (mine are) I would suggest you engage a consultant, have em
sign a non-disclosure, and start going over your requirements - if for
NOTHING ELSE than to fully write out the requirements document. Then,
when you have a requirements document, you can make some other decisions
about what kind of server to use, what kind o codebase will be useful and
where, etc etc.
My apologies if the above sounded 'harsh' - but 'to provide a web service'
usually makes me beg the question - uh - how is a client going to actually
access the data?
Good Luck !
Mondo Regards [Bill]
--
William Sanders / efGroup {rmv the DOT BOB to reply}
VFP Webhosting? You BET! -> http://efgroup.net/vfpwebhosting
Failing dotNet Project? -> http://www.dotnetconversions.com
_______________________________________________
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
** 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.
