>1. Auto increment primary key field - when I built the package, this came up as regular field and it didn't work quite well when I tried to insert record when the data was SQL Server

If anything auto-increment in SQL Server should be more reliable than in FoxPro. ANd if that doesn't work for your situation you can use a stored proc to increment a counter (I do that in my business objects actually to get Ids passed back before an insert actually occurs).

>2. The issue with the date I have which goes centuries in the back. I would have to split the date time field into a date time field + an integer field to be able to support dates such as April 1st, 1460.

Do you really need dates that go that far back? The SQL DateTime data type goes back Jauary 1, 1753 according to the documentation.

>3. Overall knowledge of data maintenance, doing backups, recreate tags, etc.

I think you're making this harder than it has to be <s>... If anything a lot of these things are easier because you don't have to write code to do it but can use the admin tools which are pretty easy to set up. Sure, you can have an Admin do that, but it's not necessary especially if you compare it to the level at which you'd do this with FoxPro data.

All of the Admin functionality can also be driven through code although it takes some scouring to find the right things to call.

I say all of that because I tended to stick with FoxPro data for most of my Fox work as well although I started using SQL at some point. However, after having spend more time with SQL Server I find I miss many of the features in FoxPro.

>Then, to that, I have an issue with the licensing issues. Some recommended to go with the Express version. I am really not sure about that. I also have two CPUs. So, this would mean it would cost me double as far as licensing goes.

There's that and that's definitely an issue especially for Web applications. But keep in mind the time you are wasting right now and what that adds up to. And in the end the OleDb provider is just not a good choice for high end data access. It'll just cause you all sorts of grief down the road.

It's a different story with Fox data driven through COM or VFP, but the OleDb driver is just a scary thing <g>...