Can you explain it to reseller's why we need patch ????

Your reseller is correct. Do not fix what is not broke. Microsoft sends patches to fix very specific issues, which may not be applicable for you in the way that you use RMS. Also your reseller needs to have time to test the patch to make sure that it is not breaking anything that you do need and work with on daily base.

So, it is safe to say that whatever patches have microsoft release, I have to isolate the problem first before applying the patches??? Most of the user of MRMS have started from RMS v1.3R.0203 ...have been able to detect the problem at the long run , then they apply the new release patch.Do you mean I have to wait and dig deeper to find the problem of the verison i'm using before updating it. Is it good to find some preventive measure than waiting for a cure of it?Knowing that some MRMS users have experience the problem already. For sure the patches that microsoft have been release serves its' purpose and it is there for a reason. Does the patches that microsoft have been releasing is not yet tested ? That's why reseller needs more time to test it? Is there different way of running the application that you might think , so that I can make sure that those problems that was face by other user , i can prevent it or I will not experience the same fate as theirs.

Will the patches that microsoft has release ,once installed, might affect the performance of MRMS ??? Even I haven't isolated the problem.

"Afsh> Your reseller is correct. Do not fix what is not broke. Microsoft sends

I say if you are having some sort of problem go ahead with the latest patch if those patches list fixes for the problem. The patches are cumulative so even if you install a specific patch for a specific problem you are still installing all the patches up to that point along with it. If each patch was one individual fix it would be different and a I'd say just install the ones you need, but since that isn't the case I'd install the latest one if you are having a problem it may fix and don't worry about it otherwise.

A reseller may have a custom add-on that they have written for a customer for use with their installation of RMS. The add-on could be adversely affected by the patch itself.

Obviously Microsoft would have no way of testing their hotfix with all of the customizations out there, let alone one. That sort of testing would have to be done by the reseller. From this perspective, most users, esp. those with customizations, will want to wait for their reseller to test rather than installing the hotfix, running into a problem, having to uninstall...

That by itself is a good reason to wait for testing before jumping in, unless you currently have a critical problem affecting your operations, and the hotfix has to be installed to take care of it

kev> I say if you are having some sort of problem go ahead with the latest patch

Our setup is a plain installation...no addon was there....

My questi> A reseller may have a custom add-on that they have written for a customer for

I'm sure that you already know by now that once you update one location, you need to update all locations in an HQ environment - otherwise you will start getting errors between HQ Server and HQ Client.

I guess I'm echoing what was said before, but I only install HOT FIXES if a customer is experiencing a problem that has been fixed since the current installed version.

SERVICE PACKS are a different matter. MS does much more rigorous testing when labeling an update as a service pack than they do for the more frequent hot fixes. Sometimes an actual new feature will sneak into a service pack as well.

Now, sometimes a hot fix will resolve an issue that wasn't listed as having been fixed. 1.3R1 introduced a bug in printing using Text based label printers (cognitive, Zebra, etc.). This bug was never listed as fixed, but the first hot fix did resolve it. I didn't know that until we tested it locally.

Anyway, your reseller knows your situation far better than anyone here or anyone at Microsoft. You're kind of asking us to second guess their specific knowledge of your install based on general knowledge of what happens generically. Also, your partner has a lot more at risk than anyone (except you of course) if you go ahead and update and then something DOES break - with 29 locations, I would be very conservative on changing anything! It looks to me like you are getting pretty sound advice from your partner; maybe just not the world's best presentation...

Glenn Adams Tiber Creek C> Our setup is a plain installation...no addon was there....

Let me bring you in the past..Atleast it will give you some insight.... :<

Before I joined my current company, 2 years of using MRMS v1.2 then 1.3R. there are several problems that I have experience in my previous company. One major problem was (v1.2) that the Inventory Transfer Order(records) are not reaching to receiving shop (missing inventory transfer out, i even posted this question !).

After updating 1.3R , that problem was resolved,but a new problem came..though Inventory Transfer Order was received (record wise) but it is empty both HQ data and Receiving shop data plus in store level commiting 1 particular Inventory Transfer Order with 10 records it takes a lot of time. That was after 1.3R !!!!!

Since then I was checking regularly in this newgroup, people here are talking about patches that solves some problems. Then at that point I was asking my reseller that there was a newsgroup in Microsoft that was talking about some patches.I told them maybe it might help us in our current situatiion. But no one has responded from them until I was recruited to handle a new set of setup using the same software but with 1.3Rv.0203 which is the version that I was using before I transfered.

Since I know the problem before hand ,I was asking this patches badly. Because I don't have time to isolate the problem agian and again knowing that problem is there.

Now, you tell me if it is a sound advice coming from my reseller ????

thanks

"Glenn Adams [MVP - Retail Mgmt]" wrote: