Do you mean aside from the fact that it requires the Enterprise version of SQL Server?

Usually, when an .LDB file is still around, the Access database was not closed properly. Standard way of fixing the problem is to delete the LDB file and then...

Maybe the best way to handle this is to put your read only tables in one or more filegroups that are separate from your read/write tables. Then you can...

use the same password on both servers or set up impersonation.

I would say so... Question 3 is a dead giveaway.

Answering this is likely not going to get me anywhere, but anyway...

I agree with everyone else... There's just no way around it: T-SQL is a LOT more flexible and powerful...

Evaluation editions are fully functional - the only limitation is that the license is only good for 180 or so days.

FWIW, I rebuilt the VM, and only installed Ofc 2007, and it worked fine.

this is gonna sound somewhat contrarian, but oh well...

Certifications are so-so. Experience trumps certifications almost every time. I know an MVP here in town that has zero certifications,...

Maybe I don't get it, but are you saying "I understand that I should normalize, but I don't want to."? It would be easier to delete a single child...

I would normalize and create a child table for the names. Then you can set the size to something sensible, like VARCHAR(25) or smaller for FirstName and LastName columns.

You can probably do it with a combination of LEFT, RIGHT, and CHARINDEX

The ONLY difference between LIKE in SQL Server and LIKE in Access is the wildcard character...

Access uses * for a wildcard and SQL Server uses %

Developer is SUPER cheap... like $40-60. Definitely worth the investment if you want to learn SQL Server.

This looks remarkably like a homework assignment... have you covered the GROUP BY clause yet?