|
|
Posted by Sandman on 09/07/05 17:29
In article <1125886481.483240.171420@o13g2000cwo.googlegroups.com>,
"weissborn@charter.net" <weissborn@charter.net> wrote:
> I have an application I have written in MS Access 2002. It is a very
> basic inventory system for keeping track of information about our
> Unix(solaris to be specific) servers. Other admins may want to use it
> shortly and running MS Access over the WAN is no picnic. It was
> suggested that I port to php and MySql. Having no experience with
> either, I'm wondering if this is a viable solution.
>
> The database if very "plain vanilla", i.e., bascially a flat file
> although a few tables with foreign keys relating to the main table. No
> fancy reporting just a few basic queries such as "show all systems
> marked as servers running version X of software Y" type of thing. Some
> of the forms have some VBA code behind them that do simple things like
> change the color of the text to make it stand-out. This data/web-page
> would only be used internally.
>
> >From what I've read so far, php looks like it may be a good way to go
> but I'm not sure. What say you all?
>
> Any suggestions, comments, concerns would be most welcome as well as
> pointers to sites that might be doing something similar.
We're awfully biased towards php in this group - so the answer is a simple
"Yes" :)
I always like to keep my options open for future development, s while some data
might not directly require a SQL database, I like to put it there anyway, since
I often end up wanting to make it more advance in the future.
Plus, with SQL, you get the whole fetch/update/insert API built in. You don't
have to build own tools to lookup data in flatfiles.
--
Sandman[.net]
Navigation:
[Reply to this message]
|