I have two unrelated questions. I have been using the previous version for a while but finally got an unlimited registration after switching to 3.0 and am now starting to use more of the features of the program and am running into a few questions.

First is about tags, I added some tags and then tagged a few dvds but when i went to filters I could not get it to show me just the dvds with that tag. I did see the another post on tags and that seemed to clear up the checkmarks (checked, unchecked, grayed) but people also said they were filtering on that which I cant seem to get to work so i figure i'm doing something wrong. Also, if i have a tag with a child tag, can i tag the dvd with just the child tag or does it need the parent checked as well? Additionally when I just installed on Vista it no longer has the filter section over the collection list, i can only see one or the other, not both at the same time.

Second question is related to box sets and child profiles under them, is there a good thread on setting this up? I have various box sets that I have added to my collection, but this only shows the box set in my collection and not the movies contained in that box set. From my understanding having them as a child profile will do this, but my question is how do I add the child profiles (I've seen stuff about by disc id or by the individual movies profile)

-Agrare

Quoting ya_shin:

Quote:
Note: Always watch out not to confuse the Filter and the Set Tag windows. It is a common mistake and can easily happen.

Very true. I strongly recommend moving the Set Tags window somewhere else in your layout. If it isn't tabbed with Filters, it is much less likely that you will confuse them.

thank's that's exactly what I was looking for.

one more question regarding box sets. How is purchase price/date/place handled for the children? should i leave them all blank? will they inherit the parent set's data for that? My concern is for how it shows on reports. Mainly with purchase price, if i buy a 2 movie box set for $20 do i just set the box sets purchase price as 20 or do i set each child to 10? if i do both, will it show on a report as $40 total spent?

-Agrare

Quoting Agrare:

Quote:
thank's that's exactly what I was looking for.

No problem; glad you got it sorted.

Quote:
one more question regarding box sets. How is purchase price/date/place handled for the children? should i leave them all blank? will they inherit the parent set's data for that?

None of the fields are inherited; you have to enter the data by hand for each one I'm afraid.

Since this is all Personal Data and doeasn't get submitted you can handle it however you want - I believe most people do what I do (I'll get loads telling me they don't now!) and copy the parent data for date and place and set the purchase price to 0.
The alternative that some use is to set the parent profile purchase price to 0 and divide the cost amongst the child profiles.

However this does still leave one potential problem with your reports (actually more of a problem for Graphs/Charts) and that is if the children are sold separately and have their own EAN/UPC then they will have their SRP/RRP set to their separate value so your RRP totals will be the cost of the parent PLUS the cost of the children... and the Savings Report will show you've done better than you have!
If the children are not sold separately then the SRP in the central database should be 0 anyway so it's not a problem.

The easy answer is to set the SRP to 0 on the children as well as the purchase price; I believe this is one reason why SRP tends to be an auto-locked field so when you get updates to the children it doesn't overwrite the (now 0) purchase price each time. Obviously you take care not to submit this SRP update in any contributions you do for the child profiles!

Of course if you use the 'divide thepurchase price amongst the children' method it's probably better to set the RRP of the parent to 0 to match the purchase price but this still remains inaccurate actually because the total SRPs of the children is unlikely to be the SRP of the parent which is what you actually bought.

FWIW I have no idea how it treats the maths if the price is left blank rather than 0.[i][/i]