Welcome to WebmasterWorld Guest from 184.108.40.206
Forum Moderators: phranque
I have not found any good info on the website.
For you experts out there is this the best database software package for an online bookstore out there at a reasonable price and does it allow you to customize or am I better off building my site from scratch and putting all the bells and whistles I need.
Any advice from you experts would be great
However, the database is only the repository for the data. You then need a language/system to get the data into web pages. ASP (Active Server Pages) is nostly used with Access and its big brother SQLserver, whilst Lasso is mostly used with FileMaker Pro.
Interestingly, I stumbled across another system yesterday that can be used with any ODBC database via CGI called WhizBase [whizbase.com] which may be worth checking out.
I would suggest that you need to do some more research into each of the database/system combinations before making a final decision. Do some seaches on google for MS Access, Active Server Pages, FileMaker Pro, and so on and read up on it all.
Hope this helps,
(BTW Bob, are you sure that Access is not a true relational database? What is the definition of a true relational database? )
Disclaimer: I have no connection with any of the programs mentioned here....
What I meant to say is that Access is not a client/server RDBMS.
A friend of mine came to me for some advice - he was using Access - and asked why it was so slow. He did not realize that all processing is done on the client: entire tables are sent to perform joins and queries on the client, as opposed to a client/server model, where the processing is done on the server and the only data transfer is/are the final result rows themselves.
Woz has given you some good examples, my suggestion is that you stick with a client/server model and forget Access.
I used to wake up at nights having nightmares about databases, i'm not joking either :)
Bob, could you give some examples of this? Have you used Access yourself?
I use ASP technology where ALL the processing is done on the server and plain HTML is sent to the client.
TPK >20 tables, 120k rows, 10 columns
I agree that if your database gets to this size then you should migrate to something more robust. But for small to medium size database I see no problem. A similar question was asked re Access vs SQLserver here [webmasterworld.com].