Vantage 8.03.404 - multi level MOM's

Yahoo Archive
1
If you uncheck the box for PULL AS ASSEMBLY for the component under the parent MOM, a separate job should be created to create this assembly separately.
For example, if I have a "switch assembly" that is part of the bom for the "Machine assembly" and PULL AS ASSEMBLY is unchecked for the switch assy in the machine assy MOM, a separate planning job would be done for the switch assembly when it is needed for the machine. In my case, I have the MRP planning for the switch assy part number to MRP planning quantity of 10. So, if for the machine assy 1 is needed, it will create a separate job for 10 switch assemblies, whose required date is early enough to meet the required date for the operation where the switch assembly is needed in the machine assembly.

Confusing?
Carey


To: vantage@yahoogroups.comFrom: ckrusen@...: Mon, 14 Apr 2008 20:11:18 +0000Subject: [Vantage] Re: Vantage 8.03.404 - multi level MOM's




On this topic of Multi-level MOMs....What is the difference between adding a manufactured part(that has child components) as a 'Material' vs adding it as an 'Assembly'?Will having a manufactued part as an assembly force a job to be created, even if the manufactured part is stocked and QOH is available?Calvin--- In vantage@yahoogroups.com, Carey S <rotary1@...> wrote:>> According to the documentation, this is controlled by the USE PART REVISION on the part master for that record.> If this is not selected, it will create the job or supply order based on the explicitly selected revision in the sales order.> Carey> > > To: vantage@...: manasa@...: Mon, 14 Apr 2008 08:48:21 -0500Subject: RE: [Vantage] Re: Vantage 8.03.404 - multi level MOM's> > > > > If you change a subcomponent in a MOM, it will automatically change anyMOM that uses it. At least it does in 8.00. Maybe it was a change theymade in programming?Our issue is that it uses the latest rev. I have yet to play with it ifI have multiple approved revs for the subcomponent.M. Manasa Reddymanasa@...: 630-806-2000F: 630-806-2001________________________________From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On BehalfOf c.chestSent: Monday, April 14, 2008 6:57 AMTo: vantage@...: [Vantage] Re: Vantage 8.03.404 - multi level MOM'sThe bills are pretty straight forward. For example...If part A is made up of one component...say A1, and part A is used to make part B. If I create the relationship between part B and part A in Method of Mfg and save it. Then I go back and create the relationship between part A and A1. If I look at the MOM for part B, it will not show me that part A has any components. If this doesn't happen in your system, maybe I'm doing something wrong.--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,Robert Brown <robertb_versa@> wrote:>> That is generally not true unless you use troublesome combo's of pull/view as assy and phantom/non-stock levels.> > "c.chest" <c.chest@> wrote: I have a question regarding multi-level MOM's. I am seeing that you > have to start from the ground level meaning any manufactured > components have to have their MOM completed before attaching to a > parent part. If you create the component MOM after attaching it to a > parent, it won't update the multi-level MOM of the parent part. Is > this the way Vantage works, or am I missing something. Is it really > necessary to have to un-attach a part and then re-attach it if there > is a change in the component MOM?> > > > > > > ---------------------------------> You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.> > [Non-text portions of this message have been removed]>[Non-text portions of this message have been removed] > > > > > > > __________________________________________________________> Get in touch in an instant. Get Windows Live Messenger now.> http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008> > [Non-text portions of this message have been removed]>






_________________________________________________________________
Get in touch in an instant. Get Windows Live Messenger now.
http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008

[Non-text portions of this message have been removed]
2
I have a question regarding multi-level MOM's. I am seeing that you
have to start from the ground level meaning any manufactured
components have to have their MOM completed before attaching to a
parent part. If you create the component MOM after attaching it to a
parent, it won't update the multi-level MOM of the parent part. Is
this the way Vantage works, or am I missing something. Is it really
necessary to have to un-attach a part and then re-attach it if there
is a change in the component MOM?
3
I guess I am missing something here. We have never had to do that, however,
we are only at version 8.03.403d. Maybe it is an issue with .404. I had
other large issues with .404 is why we are not to that level yet. I can
definitely tell you that is not by design and that if it is doing that it is
a major, major bug.



_____

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
c.chest
Sent: Friday, April 04, 2008 11:04 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Vantage 8.03.404 - multi level MOM's



I have a question regarding multi-level MOM's. I am seeing that you
have to start from the ground level meaning any manufactured
components have to have their MOM completed before attaching to a
parent part. If you create the component MOM after attaching it to a
parent, it won't update the multi-level MOM of the parent part. Is
this the way Vantage works, or am I missing something. Is it really
necessary to have to un-attach a part and then re-attach it if there
is a change in the component MOM?





[Non-text portions of this message have been removed]
4
That is generally not true unless you use troublesome combo's of pull/view as assy and phantom/non-stock levels.

"c.chest" <c.chest@...> wrote: I have a question regarding multi-level MOM's. I am seeing that you
have to start from the ground level meaning any manufactured
components have to have their MOM completed before attaching to a
parent part. If you create the component MOM after attaching it to a
parent, it won't update the multi-level MOM of the parent part. Is
this the way Vantage works, or am I missing something. Is it really
necessary to have to un-attach a part and then re-attach it if there
is a change in the component MOM?






---------------------------------
You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.

[Non-text portions of this message have been removed]
5
The bills are pretty straight forward. For example...If part A is
made up of one component...say A1, and part A is used to make part
B. If I create the relationship between part B and part A in Method
of Mfg and save it. Then I go back and create the relationship
between part A and A1. If I look at the MOM for part B, it will not
show me that part A has any components. If this doesn't happen in
your system, maybe I'm doing something wrong.

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:
>
> That is generally not true unless you use troublesome combo's of
pull/view as assy and phantom/non-stock levels.
>
> "c.chest" <c.chest@...> wrote: I have a question
regarding multi-level MOM's. I am seeing that you
> have to start from the ground level meaning any manufactured
> components have to have their MOM completed before attaching to a
> parent part. If you create the component MOM after attaching it to
a
> parent, it won't update the multi-level MOM of the parent part. Is
> this the way Vantage works, or am I missing something. Is it
really
> necessary to have to un-attach a part and then re-attach it if
there
> is a change in the component MOM?
>
>
>
>
>
>
> ---------------------------------
> You rock. That's why Blockbuster's offering you one month of
Blockbuster Total Access, No Cost.
>
> [Non-text portions of this message have been removed]
>
6
If you change a subcomponent in a MOM, it will automatically change any
MOM that uses it. At least it does in 8.00. Maybe it was a change they
made in programming?

Our issue is that it uses the latest rev. I have yet to play with it if
I have multiple approved revs for the subcomponent.



M. Manasa Reddy
manasa@...
P: 630-806-2000
F: 630-806-2001


________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of c.chest
Sent: Monday, April 14, 2008 6:57 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Vantage 8.03.404 - multi level MOM's



The bills are pretty straight forward. For example...If part A is
made up of one component...say A1, and part A is used to make part
B. If I create the relationship between part B and part A in Method
of Mfg and save it. Then I go back and create the relationship
between part A and A1. If I look at the MOM for part B, it will not
show me that part A has any components. If this doesn't happen in
your system, maybe I'm doing something wrong.

--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,
Robert Brown <robertb_versa@...>
wrote:
>
> That is generally not true unless you use troublesome combo's of
pull/view as assy and phantom/non-stock levels.
>
> "c.chest" <c.chest@...> wrote: I have a question
regarding multi-level MOM's. I am seeing that you
> have to start from the ground level meaning any manufactured
> components have to have their MOM completed before attaching to a
> parent part. If you create the component MOM after attaching it to
a
> parent, it won't update the multi-level MOM of the parent part. Is
> this the way Vantage works, or am I missing something. Is it
really
> necessary to have to un-attach a part and then re-attach it if
there
> is a change in the component MOM?
>
>
>
>
>
>
> ---------------------------------
> You rock. That's why Blockbuster's offering you one month of
Blockbuster Total Access, No Cost.
>
> [Non-text portions of this message have been removed]
>






[Non-text portions of this message have been removed]
7
When you set up the relationship between B and A, did you check "view as
assembly" or "pull as assembly" on part A? If you don't, it will just
show in your bill structure like it is a material. If either of the
assembly check boxes are active, you will also see the entire bill
structure of A when you are looking at part B. Even if the boxes aren't
checked, the bill structure is still there, it's just not visible.


Amy O'Malley
Process Engineer
Heraeus Medical Components Division
Lino Lakes, Minnesota
amy.omalley@...

________________________________

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of c.chest
Sent: Monday, April 14, 2008 6:57 AM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Vantage 8.03.404 - multi level MOM's



The bills are pretty straight forward. For example...If part A is
made up of one component...say A1, and part A is used to make part
B. If I create the relationship between part B and part A in Method
of Mfg and save it. Then I go back and create the relationship
between part A and A1. If I look at the MOM for part B, it will not
show me that part A has any components. If this doesn't happen in
your system, maybe I'm doing something wrong.
8
According to the documentation, this is controlled by the USE PART REVISION on the part master for that record.
If this is not selected, it will create the job or supply order based on the explicitly selected revision in the sales order.
Carey


To: vantage@yahoogroups.comFrom: manasa@...: Mon, 14 Apr 2008 08:48:21 -0500Subject: RE: [Vantage] Re: Vantage 8.03.404 - multi level MOM's




If you change a subcomponent in a MOM, it will automatically change anyMOM that uses it. At least it does in 8.00. Maybe it was a change theymade in programming?Our issue is that it uses the latest rev. I have yet to play with it ifI have multiple approved revs for the subcomponent.M. Manasa Reddymanasa@...: 630-806-2000F: 630-806-2001________________________________From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On BehalfOf c.chestSent: Monday, April 14, 2008 6:57 AMTo: vantage@yahoogroups.comSubject: [Vantage] Re: Vantage 8.03.404 - multi level MOM'sThe bills are pretty straight forward. For example...If part A is made up of one component...say A1, and part A is used to make part B. If I create the relationship between part B and part A in Method of Mfg and save it. Then I go back and create the relationship between part A and A1. If I look at the MOM for part B, it will not show me that part A has any components. If this doesn't happen in your system, maybe I'm doing something wrong.--- In vantage@yahoogroups.com <mailto:vantage%40yahoogroups.com> ,Robert Brown <robertb_versa@...> wrote:>> That is generally not true unless you use troublesome combo's of pull/view as assy and phantom/non-stock levels.> > "c.chest" <c.chest@...> wrote: I have a question regarding multi-level MOM's. I am seeing that you > have to start from the ground level meaning any manufactured > components have to have their MOM completed before attaching to a > parent part. If you create the component MOM after attaching it to a > parent, it won't update the multi-level MOM of the parent part. Is > this the way Vantage works, or am I missing something. Is it really > necessary to have to un-attach a part and then re-attach it if there > is a change in the component MOM?> > > > > > > ---------------------------------> You rock. That's why Blockbuster's offering you one month of Blockbuster Total Access, No Cost.> > [Non-text portions of this message have been removed]>[Non-text portions of this message have been removed]






_________________________________________________________________
Get in touch in an instant. Get Windows Live Messenger now.
http://www.windowslive.com/messenger/overview.html?ocid=TXT_TAGLM_WL_Refresh_getintouch_042008

[Non-text portions of this message have been removed]
9
On this topic of Multi-level MOMs....

What is the difference between adding a manufactured part(that has
child components) as a 'Material' vs adding it as an 'Assembly'?

Will having a manufactued part as an assembly force a job to be
created, even if the manufactured part is stocked and QOH is
available?

Calvin

--- In vantage@yahoogroups.com, Carey S <rotary1@...> wrote:
>
> According to the documentation, this is controlled by the USE PART
REVISION on the part master for that record.
> If this is not selected, it will create the job or supply order
based on the explicitly selected revision in the sales order.
> Carey
>
>
> To: vantage@...: manasa@...: Mon, 14 Apr 2008 08:48:21 -
0500Subject: RE: [Vantage] Re: Vantage 8.03.404 - multi level MOM's
>
>
>
>
> If you change a subcomponent in a MOM, it will automatically
change anyMOM that uses it. At least it does in 8.00. Maybe it was a
change theymade in programming?Our issue is that it uses the latest
rev. I have yet to play with it ifI have multiple approved revs for
the subcomponent.M. Manasa Reddymanasa@...: 630-806-2000F: 630-806-
2001________________________________From: vantage@yahoogroups.com
[mailto:vantage@yahoogroups.com] On BehalfOf c.chestSent: Monday,
April 14, 2008 6:57 AMTo: vantage@...: [Vantage] Re: Vantage
8.03.404 - multi level MOM'sThe bills are pretty straight forward.
For example...If part A is made up of one component...say A1, and
part A is used to make part B. If I create the relationship between
part B and part A in Method of Mfg and save it. Then I go back and
create the relationship between part A and A1. If I look at the MOM
for part B, it will not show me that part A has any components. If
this doesn't happen in your system, maybe I'm doing something wrong.-
-- In vantage@yahoogroups.com <mailto:vantage%
40yahoogroups.com> ,Robert Brown <robertb_versa@> wrote:>> That is
generally not true unless you use troublesome combo's of pull/view
as assy and phantom/non-stock levels.> > "c.chest" <c.chest@> wrote:
I have a question regarding multi-level MOM's. I am seeing that you
> have to start from the ground level meaning any manufactured >
components have to have their MOM completed before attaching to a >
parent part. If you create the component MOM after attaching it to a
> parent, it won't update the multi-level MOM of the parent part. Is
> this the way Vantage works, or am I missing something. Is it
really > necessary to have to un-attach a part and then re-attach it
if there > is a change in the component MOM?> > > > > > > -----------
----------------------> You rock. That's why Blockbuster's offering
you one month of Blockbuster Total Access, No Cost.> > [Non-text
portions of this message have been removed]>[Non-text portions of
this message have been removed]
>
>
>
>
>
>
> _________________________________________________________________
> Get in touch in an instant. Get Windows Live Messenger now.
> http://www.windowslive.com/messenger/overview.html?
ocid=TXT_TAGLM_WL_Refresh_getintouch_042008
>
> [Non-text portions of this message have been removed]
>
10
If you set it up as "Pull as Assembly", yes a subassembly job will be
created with the top level job regardless of stock on hand. The planner
would have to adjust the subassembly portion of the job to use the stock
instead of manufacturing the parts on the job.

For the type of business we do (contract manufacturing for medical
devices), my "pull as" rules of thumb are:

Material:
* The same part is used in multiple assembly part numbers and it makes
the most sense to run in large combined lot quantities.
* The top level is an assembly with a few components that may have
unpredictable usages/or the manufacturing process to make the components
isn't rock solid. It's easier to me to set the parts up as materials,
then issue a few extra pieces of the necessary components to complete
the number of assemblies we need. We've had cases where you need a left
and right half to make an assembly, and we set up the two parts as "pull
as assembly" on the top level, then ended up scrapping the entire job of
left hand parts on the subassembly--now you are stuck with an orphan
right half and really no nice, clean way to remake the left either on
the subassembly or on another job.
* It is a complex assembly i.e. 20 different components--just too hard
to make 20 subassemblies of the top job and not mess it up. Each part is
set up to run to stock and on the top level the parts are set up as
materials. Keeps the complexity to a minimum for us.

Assembly:
* The part is only used in that one assembly and no where else.
* The part is used in a few assemblies, but there's no advantage to
running in larger lot sizes
* We don't want subassembly stock on-hand (expensive part, risk
customer might change design and no commitment to take product beyond
finished goods, etc.)
* We want to save the extra receipt of subassembly to stock and issuing
to top level assembly job steps

Not all inclusive, but my $0.02...

Amy O'Malley
Process Engineer
Heraeus Medical Components Division
Lino Lakes, Minnesota
amy.omalley@...

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Calvin Krusen
Sent: Monday, April 14, 2008 3:11 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Re: Vantage 8.03.404 - multi level MOM's

On this topic of Multi-level MOMs....

What is the difference between adding a manufactured part(that has
child components) as a 'Material' vs adding it as an 'Assembly'?

Will having a manufactued part as an assembly force a job to be
created, even if the manufactured part is stocked and QOH is
available?

Calvin
11
I haven't seen behavior like that in 404.

Are you sure the part A & A1 Rev is approved, active and the part A MoM is the primary for the active/approved rev?

Other things to check:

* Effective date of active/approved Rev for part A must be less than or equal to system's current date.

* No other approved Rev's exist for part A or A1. (If they do, the lowest alphanumeric Rev is used by MRP, Order Job Wizard and Mehtod Display - suggesting the 'lower' active Rev has no MoM details.)

* Part A1 is not a phantom.

* Try the 4 different combo's of Part A as phantom/non-phantom and whether it is set to Pull as Assembly or not.

If you have odbc (or access to create BAQs) write a few simple table dump (all columns) queries to compare the Part, Part Plant, Part Rev, PartDtl table records of your new parts A, B & A1 to existing parts that behave/display the way you want them to.

You'll likely find one (or more) field values set up differently for your new parts that is causing the behavior you are experiencing.

Rob Brown

"c.chest" <c.chest@...> wrote:
The bills are pretty straight forward. For example...If part A is
made up of one component...say A1, and part A is used to make part
B. If I create the relationship between part B and part A in Method
of Mfg and save it. Then I go back and create the relationship
between part A and A1. If I look at the MOM for part B, it will not
show me that part A has any components. If this doesn't happen in
your system, maybe I'm doing something wrong.

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:
>
> That is generally not true unless you use troublesome combo's of
pull/view as assy and phantom/non-stock levels.
>
> "c.chest" <c.chest@...> wrote: I have a question
regarding multi-level MOM's. I am seeing that you
> have to start from the ground level meaning any manufactured
> components have to have their MOM completed before attaching to a
> parent part. If you create the component MOM after attaching it to
a
> parent, it won't update the multi-level MOM of the parent part. Is
> this the way Vantage works, or am I missing something. Is it
really
> necessary to have to un-attach a part and then re-attach it if
there
> is a change in the component MOM?
>
>
>
>
>
>
> ---------------------------------
> You rock. That's why Blockbuster's offering you one month of
Blockbuster Total Access, No Cost.
>
> [Non-text portions of this message have been removed]
>





between 0000-00-00 and 9999-99-99

[Non-text portions of this message have been removed]
12
Thank you all very much for the responses. I will go back and do
more testing using the information you all have provided. I'm glad
to hear that it just may be something I coded wrong instead of the
system being set up to act this way.

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:
>
> I haven't seen behavior like that in 404.
>
> Are you sure the part A & A1 Rev is approved, active and the
part A MoM is the primary for the active/approved rev?
>
> Other things to check:
>
> * Effective date of active/approved Rev for part A must be less
than or equal to system's current date.
>
> * No other approved Rev's exist for part A or A1. (If they do,
the lowest alphanumeric Rev is used by MRP, Order Job Wizard and
Mehtod Display - suggesting the 'lower' active Rev has no MoM
details.)
>
> * Part A1 is not a phantom.
>
> * Try the 4 different combo's of Part A as phantom/non-phantom
and whether it is set to Pull as Assembly or not.
>
> If you have odbc (or access to create BAQs) write a few simple
table dump (all columns) queries to compare the Part, Part Plant,
Part Rev, PartDtl table records of your new parts A, B & A1 to
existing parts that behave/display the way you want them to.
>
> You'll likely find one (or more) field values set up differently
for your new parts that is causing the behavior you are experiencing.
>
> Rob Brown
>
> "c.chest" <c.chest@...> wrote:
> The bills are pretty straight forward. For example...If
part A is
> made up of one component...say A1, and part A is used to make part
> B. If I create the relationship between part B and part A in
Method
> of Mfg and save it. Then I go back and create the relationship
> between part A and A1. If I look at the MOM for part B, it will
not
> show me that part A has any components. If this doesn't happen in
> your system, maybe I'm doing something wrong.
>
> --- In vantage@yahoogroups.com, Robert Brown <robertb_versa@>
> wrote:
> >
> > That is generally not true unless you use troublesome combo's of
> pull/view as assy and phantom/non-stock levels.
> >
> > "c.chest" <c.chest@> wrote: I have a question
> regarding multi-level MOM's. I am seeing that you
> > have to start from the ground level meaning any manufactured
> > components have to have their MOM completed before attaching to
a
> > parent part. If you create the component MOM after attaching it
to
> a
> > parent, it won't update the multi-level MOM of the parent part.
Is
> > this the way Vantage works, or am I missing something. Is it
> really
> > necessary to have to un-attach a part and then re-attach it if
> there
> > is a change in the component MOM?
> >
> >
> >
> >
> >
> >
> > ---------------------------------
> > You rock. That's why Blockbuster's offering you one month of
> Blockbuster Total Access, No Cost.
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> between 0000-00-00 and 9999-99-99
>
> [Non-text portions of this message have been removed]
>
13
Thank you all very much for the responses. I will go back and do
more testing using the information you all have provided. I'm glad
to hear that it just may be something I coded wrong instead of the
system being set up to act this way.

--- In vantage@yahoogroups.com, Robert Brown <robertb_versa@...>
wrote:
>
> I haven't seen behavior like that in 404.
>
> Are you sure the part A & A1 Rev is approved, active and the
part A MoM is the primary for the active/approved rev?
>
> Other things to check:
>
> * Effective date of active/approved Rev for part A must be less
than or equal to system's current date.
>
> * No other approved Rev's exist for part A or A1. (If they do,
the lowest alphanumeric Rev is used by MRP, Order Job Wizard and
Mehtod Display - suggesting the 'lower' active Rev has no MoM
details.)
>
> * Part A1 is not a phantom.
>
> * Try the 4 different combo's of Part A as phantom/non-phantom
and whether it is set to Pull as Assembly or not.
>
> If you have odbc (or access to create BAQs) write a few simple
table dump (all columns) queries to compare the Part, Part Plant,
Part Rev, PartDtl table records of your new parts A, B & A1 to
existing parts that behave/display the way you want them to.
>
> You'll likely find one (or more) field values set up differently
for your new parts that is causing the behavior you are experiencing.
>
> Rob Brown
>
> "c.chest" <c.chest@...> wrote:
> The bills are pretty straight forward. For example...If
part A is
> made up of one component...say A1, and part A is used to make part
> B. If I create the relationship between part B and part A in
Method
> of Mfg and save it. Then I go back and create the relationship
> between part A and A1. If I look at the MOM for part B, it will
not
> show me that part A has any components. If this doesn't happen in
> your system, maybe I'm doing something wrong.
>
> --- In vantage@yahoogroups.com, Robert Brown <robertb_versa@>
> wrote:
> >
> > That is generally not true unless you use troublesome combo's of
> pull/view as assy and phantom/non-stock levels.
> >
> > "c.chest" <c.chest@> wrote: I have a question
> regarding multi-level MOM's. I am seeing that you
> > have to start from the ground level meaning any manufactured
> > components have to have their MOM completed before attaching to
a
> > parent part. If you create the component MOM after attaching it
to
> a
> > parent, it won't update the multi-level MOM of the parent part.
Is
> > this the way Vantage works, or am I missing something. Is it
> really
> > necessary to have to un-attach a part and then re-attach it if
> there
> > is a change in the component MOM?
> >
> >
> >
> >
> >
> >
> > ---------------------------------
> > You rock. That's why Blockbuster's offering you one month of
> Blockbuster Total Access, No Cost.
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
>
>
> between 0000-00-00 and 9999-99-99
>
> [Non-text portions of this message have been removed]
>