Run the server from your company. Run IIS and you can write an application that sits on the server and handles live data. Your app can access the database server securely while the website delivers the data.
>Hello Everybody.
>
>For a while now I have been following with interest threads which talk about accessing data over/through/from the internet in an attempt to learn on how to do this best for my app.
>
>Maybe it would be best if I start by describing what I have in mind:
>
>I have a MRP system (manufacturing software) which I would like to upgrade with 'satellite' apps. Those would be small exe's which reside at a salesman's or customer’s workstation anywhere in the world. With those apps they could then enter orders, view inventory stock status, view their order status, etc..
>
>Now, in order for my customer not to have to buy an internet server, or having to go through the trouble to find an ISP which offers certain services needed, I though the best (and maybe easiest) way of doing this could be to connect the 'satellite' workstation with my customers workstation/server through the internet.
>
>Originally I though that should add to the security, since I have no website which someone could find, and because of this knowledge could then hack into it. however, this leaves an open connection to my customers network, which is not that great (security wise) either.
>
>Another issue is live data. My proffered way is to have up-to-date information available. If I have data on a web server, I need to update this periodically, which means it's not live data.
>
>what are the usually preferred approaches and how do I start using them?
>
>Thank you very much in advance for all your thoughts and help!
Brian Seekford
Seekford Solutions, Inc.http://www.SeekfordSolutions.comInternet ActiveX Controls and .NET Class Libraries.
SMTP/S FTP POP3/S HTTP/S SNTP MIME PING WHOIS TRACEROUTE NNTP DNS MX
Base64, UUEncode, yEnc, MD5, SHA1, URL, Quoted-Printable.
Resizer and Tooltips
Email Verification and more. Check us out!