|
|
Posted by Lionel on 11/01/06 00:37
Alex S wrote:
> Hello everyone,
> My company uses a FoxPro database right now as an interface
> and a database. For our situation, I have come to the conclusion that
> it would be a better choice for us to move to an SQL server of some
> sort. I have been given the task of overseeing the overhaul on the
> program. I am paranoid about security and uptime, and so is the CEO and
> there is more and more demand for the company to get on the interactive
> internet. I'd like our clients to be able to submit data to our
> database and pull data from it (only certain data of course). My idea
> is to convert the FP tables to and SQL server and write an internal
> application(or web-based - advantages? I dunno) for the interface. For
> the internet side of things, my idea is to have seperate web database
> (SQL) that will put information from web clients. Through the internal
> interface, internal users would then be able to pull data from the web
> database to the internal SQL. And through the internet (authenticated
> of course), the web users would pull data though the web database, who
> pulls information from the internal SQL database. Would someone please
> tear this idea apart w/ advantages and disadvantages. Also, if this is
> the best route, tell me how I can sell this idea to my boss. What's so
> good about using SQL vs. FP over the internet? What about internally?
> What about security? Cost is going to place a big role on the what the
> CEO decides, unless I can sell him otherwise. Should I tell him that we
> shouldn't do it now and save some money to do it right? Or what? Some
> help please. Thanks.
Please read http://www.catb.org/~esr/faqs/smart-questions.html
I think you may have broken every rule in the book. It's hard to say
because there is no way I'm going to read that massive chunk of text
above. Please read about cross posting.
Lionel.
Navigation:
[Reply to this message]
|