Replies

#1 - I've never heard of Notetab, but apparently it is some sort of text editor. If the text is simple enough to enter into a web form, PHP could be used.

#2. - MySQL supports multiple databases, which are specified in the SQL language. You could use distinct domain names, but that would make more sense if the databases were hosted on different servers.

#3 - I'd go with a server. If PHP is used, I'd use Linux for the operating system with Samba for file sharing with Windows clients - with per-user access privileges.

#4 - If I recall correctly, MySQL can authorize different user accounts for access at various levels - database, table, field, etc. It should not be necessary to run multiple MySQL processes to prevent unauthorized access to data.

Here is some unsolicited advice -

Rule #1 - Don't get involved with doctors who want to be computer programmers. It's always a disaster.

Rule #2 - Don't store large TIFF files in a database. Use the shared file system instead, and store a file path to the image in the database.

This web site and I disclaim any liability for the comments above. Use at your own risk.

I thought Notetab was some sort of a freeware version of some text editor? If it has some scripting capabilities, it sounds like some sort of round about way of doing things, probably, it was a 'temporary' solution of some sort.

If I understand correctly, you just want for the users to be able to view image files stored on the server in folders and open them on the client end with some sort of an app. The files are stored somewhere in the filesystem on the server. You are running XP. If all you need to do is to securely store the files, retrieve them (using a web server) on the server side, and view them using whatever viewer on the client side, I don't see the need for mysql. The filesystem security will take care of access to the files, i.e. a doctor will only be able to view his own stuff; if you are going to use Apache, there are quite a fiew security features provided with it. All you'd need would be a PHP, Perl or whatever based small app to provide some sort of web interface.

"...
2. Can I run multiple databases (Live, Test and Training) per website (http://application:9090) or do I have to have a separate website for each database (http://applicationprod:9090, http://applicationqa:9090)?
..."

You should be able to use one webserver to reach all ie. HTTP://www.application:xxxx/QA, HTTP://www.application:xxxx/PROD, etc. But running the other servers may provide further protection from accidentally putting test data into your production environment and vise versa. I assume you have user accounts setup for testing, training and production and these accounts do not span across multiple systems. I just thought I would comment on your post, as I'm currently developing a system for a small business. Hope my thoughts were useful to you in some way.

CT