If an organization were looking to build a database that people in different programs could access from different sites, would they be likely to use MS SQL Server? It's to track who's in what programs, attendance, progress, etc.

Amyliz, Here is the [link] to the IBM page that tells you how to navigate the t23 bios. You could set the date and time and see if it sticks, at least once.

Worth at least one try, if there is any life left in the batteries, it'll stay for a while.

If an organization were looking to build a database that people in different programs could access from different sites, would they be likely to use MS SQL Server? It's to track who's in what programs, attendance, progress, etc.

Maybe.

Well, how would people access the database? Would someone write dynamic web pages serve as the front end? Some other frontend?

Anyway, MS SQL Server is good, but expensive when compared to such open source databases as MySQL and PostgreSQL. But MS SQL Server is probably easier to maintain.

Your choice of frontend may influence your choice of backend. For example, if you develope an .asp application, you'd probably want MS SQL Server as a backend.

Would someone write dynamic web pages serve as the front end?

I believe this. I don't know what .asp is, or really anything else about this kind of thing, but I'm hoping to be able to say something semi-intelligent without talking to the programmer, because she scares me. They are willing to spend money, and I would think maintenance would be a concern.

The MS SQL Server webpage has some cost comparisions to other things -- Oracle and something else I forget. They're saying their product is the cheapest, obviously. Basically I just want to make sure it's a reasonable thing to use for costing out the whole project.

Well, SQL Server is cheaper than stuff like Oracle.

You could take a crash course on databases and web programming languages. Or you could just tell the developer, "This is our budget, and we expect this many users per day...." i.e. leave the specifics up to the developer.

OK, general question for other web people - which is easier to maintain? SQL Server/ASP or, say MySQL/PHP? My general experience is that the Microsoft solution is easier, at least until something goes wrong. Then you might be better off with some open source solution....

Thanks for the help.

Edit: I should say, I'm not going be all "You must use this software!" Just, "Here's what a couple of options would cost, now you figure it out."

SQL Server/ASP or, say MySQL/PHP? My general experience is that the Microsoft solution is easier, at least until something goes wrong. Then you might be better off with some open source solution....

I disagree. I think that PHP is easier to learn, and that MySQL, once installed, is pretty easy too. SQL Server isn't easy, in my experience. Just more inherently graphical.

Build your own scanning tunneling microscope: [link]

Beatles are beaten in Apple trademark ruling

The life and times (and death) of SuprNova.org.