RMS 1.x to 2.0 Upgrade Info

Dear John Martin, my nickname is also same. so let you know for testing I suggest you to use the Virtual Machine i.e. VMWare or Microsoft Virtual PC both of these software are available for 45 days. and there are couple fo way you can use them after expiry also. I used to perform test on these system and work with many system on same machine.

"John M." wrote:

I finally got my copy of 2.0 over the weekend and started looking at the documentation - or should I say lack of. For anyone upgrading from a prior release, the "Getting Started Guide" is worthless. It has NOTHING in it about upgrading. The "readme.txt" on the CD is almost as bad - it has 6 sentences on upgrading.

There are several questions what little documentation leads to:

Other ?s to come later.

--

John M.

I finally got my copy of 2.0 over the weekend and started looking at the documentation - or should I say lack of. For anyone upgrading from a prior release, the "Getting Started Guide" is worthless. It has NOTHING in it about upgrading. The "readme.txt" on the CD is almost as bad - it has 6 sentences on upgrading.

There are several questions what little documentation leads to:

Other ?s to come later.

--

John M.

Jeff, I have several add-ins that I want to make sure are going to work without any issues before I go live with the upgrade. My database is way too important than to rush into something just because someone says there's nothing to worry about. I could do this until the cows came home with 1.3 now it seems that we have no way of knowing if these minor table changes made in 2.0 have any effect on my add-ins until I install and activate. This is just not good practice. I want to see with my own eyes that everything works properly before I upgrade. I don't think that's too much to ask. If

I'm really trying to figure out what you guys are trying to test?

Just because MS labels it as a 2.0? I've been telling you guys since Dec, that it really wasn't a big deal. The major issue is the way the license has changed. Its still better than most as in most cases you buy a license _per_ machine. MS is only charging for the POS stations.

Do I like it, no, but what are you going to do. Spend more money? It makes our job harder to predict the end-users needs, but there have already been work-arounds discussed on this board for most of the issues.

Fire away!

I finally got my copy of 2.0 over the weekend and started looking at the documentation - or should I say lack of. For anyone upgrading from a prior release, the "Getting Started Guide" is worthless. It has NOTHING in it about upgrading. The "readme.txt" on the CD is almost as bad - it has 6 sentences on upgrading.

There are several questions what little documentation leads to:

Other ?s to come later.

--

John M.

One thing that comes to mind, how is someone supposed to demo the software? If you can't get into POS without activation how is someone supposed to evaluate? If there is a separate demo disc maybe we could use that to do our testing. Or is the demo disc nothing but a marketing tool? Craig

I come from a large systems background - yes those water cooled machines that filled whole rooms - and took large staffs to run. I probably have been around this stuff longer than some of you have even lived. You don't just bring in a new release of anything and slap it on a production system with the anticipation that everything works right out of the box. I consider my POS system a business critical asset (even for a one lane main counter) and don't want to take those chances.

Do you think Microsoft just slapped the code together and threw it out the door. No - even they tested it. Did it go to some early adopters - I'll bet.

I haven't even heard of the ability here to come up in "evaluation mode" to check such things.

The last RMS demo I receive was all marketting and nothing useful.

I'd be willing to give the "second" activation a try for testing now.

But there's still one big unanswered issue - can I run both 1.x and 2.0 on the same machine? Granted, I understand that the db design is slightly different, but I can take my current 1.x db - copy it/rename - then let 2.0 upgrade the "original one". I would then just have to go into the 1.x SO Admin and point to the copied 1.x db. Can both 1.x and 2.0 libraries exist on same machine? How do you prevent 2.0 install from removing 1.x?

I finally got my copy of 2.0 over the weekend and started looking at the documentation - or should I say lack of. For anyone upgrading from a prior release, the "Getting Started Guide" is worthless. It has NOTHING in it about upgrading. The "readme.txt" on the CD is almost as bad - it has 6 sentences on upgrading.

There are several questions what little documentation leads to:

Other ?s to come later.

--

John M.

John, Did you figure out what caused it to fail? Craig "John M." wrote in message news: snipped-for-privacy@TK2MSFTNGP06.phx.gbl... And why do we test. I just tried installing on a system and had the installation of SQL Server 2005 to fail. Sure would have hated that to happen on my production system and not walked through what the problem may be.

I have no idea. After much poking around it looks like it actually did install. I was able to successfully open 1.3. So this will be one of the great wonders of the world.

And they question why we want to test???

Well today I tried installing just the SQL server piece again on another system. That system already had .Net 2.0 installed, so it went right to the upgrading of MSDE to SQL Server 2005 Express. This worked without any problems, and SO 1.3 came up and worked ok.

As to why the failure message on the other system, the only think I can think of is that space was tight on that system (< 1Gb free).

But this made me start looking at any space issues now with 2.0. Space impact above and beyond 2.0 over 1.3: .Net 2.0 - 88MB SQL Server 2005 Express over MSDE - 215MB One interesting thing is that under control panel for MSDE it only reported about 70MB whereas for SQL Server 2005 Express it reports 815MB. From looking at the size of all folders under "C:\Program Files\Microsoft SQL Server", it went from 598MB to 815MB. (My prod db is a little under 500MB).