Deprecated - Database compatibility

I've setup some user profile fields and they seem to function correctly in that they show up when you enter or edit your account profile info. The problem is that they are being stored en masse in the data field in the users table. That is a messy way to access that data. I would have thought they would be stored in the profile_values table which could be accessed via sql much easier. Did I forget some setting in the drupal setup?

Thanks,

Steve

I'm looking for example of code for create forum site in PHP
thanks

Is there a easy way to do this? A simple db update should do it, but I'm not sure if it has any dependencies I might mess up.

Any help/pointer is appreciated.

Example:

node-type: blog
Vocab: Countries
US : 300 nodes
USSR: 266 nodes
India : 455 nodes

Now I'd like to add another term called Russia and move all nodes from USSR to Russia and delete the term USSR.

I'm working on a test site for a school at my church, and the guy who manages all the student info (including grades, balance, spitting out transcripts, etc) uses Access. The site will likely go on a Windows server, but I know they'll let us install PHP and Mysql. The big problem is, I don't want to make his job HARDER.

As an example, I set up a role for each class. Once the student is in a certain class, they get tagged with that Role in their profile. Once you have a role tagged to you, you can see the class files (thanks to Taxonomy Access).

But the last thing I want him to have to do is manually add a Role to 700 student profiles every quarter. The best idea I could come up with is to find a way to let Access be the front end to the actual MySQL database that runs the site (it'll be on the local network, so speed shouldn't be an issue).

I found a set that walks you through doing this, but they mention issues with Queries. Has anyone done this, and if so, were you able to run basic reports, and make changes that were reflected on the site right away?

It seems the vid should be dropped as part of the primary key in the node table. With the vid as part of the primary key that means any child entity *must (depending on how strict you want to be) have the node tables primary key as a foreign key. But since the vid is only a version number of that node entry.. other tables do not need this information. The vid field in the node table should be a foreign key of the node_revisions table and the nid field in the node_revisions table should be a foreign key from the node table (which it is already).

Drupal newbie here. I am moving my site from drupal 4.7 to 5.x. I am making a clean install for my new 5.x webpage and creating a brand new database. I decided not to upgrade from the old site, as there were MULTIPLE problems with the database and structure of my 4.7 site that I inherited when I took over the site for the non profit I'm working with. In any case, is there an easy way to import users from my old site?
My setup is as follows:
Live site: example.com (drupal 4.7)
Subdomain: test.example.com (drupal 5.1)