Headquarters

If you are an RMS reseller this should have been covered before writing your exam.

If you are a customer I would strongly recommend talking with a Certified Reseller about getting some help install. Do a google search for "Microsoft Retail Management" and you should be able to find a suitable Partner that you feal confident and comfortable with to help you out.

If you are completely absolutely against working with a Certified Reseller there are help files that come with the system that explain installation, setup and configuration.

SQL 2005 Express comes with the system, whether or not it is suitable for your operations is another story.

Robert

"Angelique" wrote:

You need to buy HQ. But when installing you need to make sure that the collation settings are the same in all stores and HQ. If you need help we can provide you web based training per hour.

Thank you..yes we are resleers..I started working here a year ago..my boss wont pay for me to train..i have to learn it all on my own..so i found this forum and I come and ask..thats why I post where I can..

thank you

"Afsh> You need to buy HQ. But when installing you need to make sure that the

"My boss won't pay for me to train...." - I can't tell you how sorry I feel reading these lines....

If you are a reseller, that means you should have access to Partnersource. There is also web-based e-learning for both Store Operations and Headquarters, at a nominal fee of about $100. You won't learn everything about the software, but you'll get a solid foundation on which to build. Do not rely on newsgroups, although yes you can get some good advice (I know I have benefitted from this newsgroup immensely) but as a reseller, you cannot afford to get wrong advice, as you run the risk of messing up your client's system. $100 for e-learning straight from MS (which you can also do on your spare time, not for your boss' benefit, but for your benefit) is a good investment. If he/she still doesn't see it this way, time to polish the good ol' resume.

But to go back to your original question, if the retailer already has three stores, running independent copies of Store Operations Manager, you have to decide which Store Ops database is the most complete and reliable, as the HQ database is created from a Store Ops database. The other two stores will then inherit their item list from a store exported from HQ. The primary reason for this is that all stores need to have the same identifier for centrally managed data (ie, items).

Earlier someone mentioned on this post to engage a RMS certified partner. HQ is not difficult to roll out, but its also not easy. It may be worth it to bring onboard someone that can get this done quick, and give you an opportunity to see what this entails.

Good luck - hope this helps....

"Angelique" wrote:

"Thank you..yes we are resleers..I started working here a year ago..my boss wont pay for me to train..i have to learn it all on my own" This just blows me away! Your boss plans on taking advantage of some unwitting retailers that think they are hiring someone that knows how to do the job. Basically they will pay you to learn on the job. Then when you screw everything up royally for them they will have to pay someone else to do the job right for them. Unbelievable.

Craig

Craig you are right. Customers be aware - ask the partner to show you the MS Certification that this person has qualified and passed the exam for Store Operation and Headquarters.

"..., if the retailer already has three stores, running independent copies of Store Operations Manager, you have to decide which Store Ops database is the most complete and reliable, as the HQ database is created from a Store Ops database. The other two stores will then inherit their item list from a store exported from HQ. The primary reason for this is that all stores need to have the same identifier for centrally managed data (ie, items)."

Does Microsoft have any tools to help merge data from existing Store Operations databases into a common Headquarters database? There are more than just items which need to be centrally managed in HQ; there's departments, categories, reason codes, tax codes, tender types, suppliers, and that's just off the top of my head.

Customer also need to come up to HQ. They do originate at the store, but if the same customer was added at two diffferent stores, and assuming they want to use global customers, is there any tool to allow you to merge these two customers into one? I don't expect this to be a single SQL script or one-click tool, but something to let you compare customer records on common fields, review the ones with the same or similar information, then decide which one to keep.

There's also the matter of bringing sales history from these stores together. since the sales at the store originated with item and customer info which wre not previously in HQ, any transaction history I try to bring in will reference the customer and item ID at the store, not the one created by HQ.

Again, I'm looking for tools that are available from Microsoft or are downloadable from PartnerSource. If I need to buy a third-party tool form someone, I'll go ahead and develop these SQL scripts and tools of my own.

Does anyone know if there is a way to stop all the components of and asssembly or a kkit item from being listed on the receipt and just to show up as the kit/assembly item name please.

OR

Maybe someone can give me some advise on how to setup our items more effectively. I have a custom prinitng/crafting business. The products I sell involve printing custom artwork for customers and the production process includes ink,scalpal blades,pvc film etc. I would like my stock to deplete as I sell items and the cashier should be able to select substitutes for certain items as the POS, but I do not want each individual item showing up, like 5ml ink, 1 blade 1 film etc. Is there any better eay to do this ?

Many thanks for any help

"..., if the retailer already has three stores, running independent copies of Store Operations Manager, you have to decide which Store Ops database is the most complete and reliable, as the HQ database is created from a Store Ops database. The other two stores will then inherit their item list from a store exported from HQ. The primary reason for this is that all stores need to have the same identifier for centrally managed data (ie, items)."

Does Microsoft have any tools to help merge data from existing Store Operations databases into a common Headquarters database? There are more than just items which need to be centrally managed in HQ; there's departments, categories, reason codes, tax codes, tender types, suppliers, and that's just off the top of my head.

Customer also need to come up to HQ. They do originate at the store, but if the same customer was added at two diffferent stores, and assuming they want to use global customers, is there any tool to allow you to merge these two customers into one? I don't expect this to be a single SQL script or one-click tool, but something to let you compare customer records on common fields, review the ones with the same or similar information, then decide which one to keep.

There's also the matter of bringing sales history from these stores together. since the sales at the store originated with item and customer info which wre not previously in HQ, any transaction history I try to bring in will reference the customer and item ID at the store, not the one created by HQ.

Again, I'm looking for tools that are available from Microsoft or are downloadable from PartnerSource. If I need to buy a third-party tool form someone, I'll go ahead and develop these SQL scripts and tools of my own.

-- Bill Yater Blue Horseshoe Solutions snipped-for-privacy@bhsolutions.com