The new version of MSPOS needs to have Parent Child Items

Posted by alyman on September 8, 2005, 6:08 pm

Please log in for more thread options

I have customers that would really like to see the Parent Child Relationship
with the new version of MSPOS. Pretty basic functionality that we need to
have the product compete in the market place.

----------------
This post is a suggestion for Microsoft, and Microsoft responds to the
suggestions with the most votes. To vote for this suggestion, click the "I
Agree" button in the message pane. If you do not see the button, follow this
link to open the suggestion in the Microsoft Web-based Newsreader and then
click "I Agree" in the message pane.

http://www.microsoft.com/Businesssolutions/Community/NewsGroups/dgbrowser/en-us/default.mspx?mid=28fd82c3-88ff-43f8-b8b2-dd30ec1a4e8a&dg=microsoft.public.pos

Posted by Jason Hunt on September 12, 2005, 9:49 am

Please log in for more thread options

Personally I think that small features like this should be left out of POS,
as they are what makes RMS worth the extra dollars. RMS should be the
feature-rich edition, and POS should be the plain-jane edition.

My impression was that POS is designed to strictly "replace a cash
register", and cash registers do not have parent/child relationships. RMS
is a "management system" where you would expect these sorts of things.

However that's just my two cents.

--
Jason Hunt
Advanced Computer Systems

Posted by Mr.J on December 10, 2006, 11:45 pm

Please log in for more thread options

I actually REALLY need this feature. As a new small business owner, I was
atrackted to POS. It look just like what we needed and with all the work to
start a business up, we went for it. Unfortunately, it's exactly one of the
features we need as we take bulk product and divide into small units for sale.

Is there a process to workaround this limitation to keep inventory acurate?
Even an outline of a manual way would help to tie the sales of the
subdivided units back to the bulk that was ordered from the vendor.
thx.
--
Mr.J

"Jason Hunt" wrote:

> Personally I think that small features like this should be left out of POS,

> as they are what makes RMS worth the extra dollars. RMS should be the

> feature-rich edition, and POS should be the plain-jane edition.

> My impression was that POS is designed to strictly "replace a cash

> register", and cash registers do not have parent/child relationships. RMS

> is a "management system" where you would expect these sorts of things.

> However that's just my two cents.

> --

> Jason Hunt

> Advanced Computer Systems

Posted by Craig on December 11, 2006, 9:02 am

Please log in for more thread options

Even if you had RMS you probably wouldn't use Parent/Child for this because
the way it works is not very efficient. I also buy seed in bulk and break it
into smaller quantities. Just have one item number for both the units and
use MPQ for ordering. I don't really know anything about POS, I just know
that Parent/Child is worthless the way it works within RMS.
Craig

>I actually REALLY need this feature. As a new small business owner, I was

> atrackted to POS. It look just like what we needed and with all the work

> to

> start a business up, we went for it. Unfortunately, it's exactly one of

> the

> features we need as we take bulk product and divide into small units for

> sale.

> Is there a process to workaround this limitation to keep inventory

> acurate?

> Even an outline of a manual way would help to tie the sales of the

> subdivided units back to the bulk that was ordered from the vendor.

> thx.

> --

> Mr.J

> "Jason Hunt" wrote:

>> Personally I think that small features like this should be left out of

>> POS,

>> as they are what makes RMS worth the extra dollars. RMS should be the

>> feature-rich edition, and POS should be the plain-jane edition.

>> My impression was that POS is designed to strictly "replace a cash

>> register", and cash registers do not have parent/child relationships.

>> RMS

>> is a "management system" where you would expect these sorts of things.

>> However that's just my two cents.

>> --

>> Jason Hunt

>> Advanced Computer Systems

Posted by Mr.J on December 11, 2006, 9:36 am

Please log in for more thread options

Craig,
Can you provide a little more detail (pardon my ignorance). You stated:
Just have one item number for both the units and
use MPQ for ordering.

1. The same item number for both the bulk and divided units OR two different
item numbers for the buld and divided units?
2. What's MPQ?
thx.
--
Mr.J

"Craig" wrote:

> Even if you had RMS you probably wouldn't use Parent/Child for this because

> the way it works is not very efficient. I also buy seed in bulk and break it

> into smaller quantities. Just have one item number for both the units and

> use MPQ for ordering. I don't really know anything about POS, I just know

> that Parent/Child is worthless the way it works within RMS.

> Craig

> >I actually REALLY need this feature. As a new small business owner, I was

> > atrackted to POS. It look just like what we needed and with all the work

> > to

> > start a business up, we went for it. Unfortunately, it's exactly one of

> > the

> > features we need as we take bulk product and divide into small units for

> > sale.

> >

> > Is there a process to workaround this limitation to keep inventory

> > acurate?

> > Even an outline of a manual way would help to tie the sales of the

> > subdivided units back to the bulk that was ordered from the vendor.

> > thx.

> > --

> > Mr.J

> >

> > "Jason Hunt" wrote:

> >

> >> Personally I think that small features like this should be left out of

> >> POS,

> >> as they are what makes RMS worth the extra dollars. RMS should be the

> >> feature-rich edition, and POS should be the plain-jane edition.

> >>

> >> My impression was that POS is designed to strictly "replace a cash

> >> register", and cash registers do not have parent/child relationships.

> >> RMS

> >> is a "management system" where you would expect these sorts of things.

> >>

> >> However that's just my two cents.

> >>

> >> --

> >> Jason Hunt

> >> Advanced Computer Systems

> >>