Part Import very Slow

Hi Bruce,

> We have a Progress db and used Pervasive and ODBC to import about
> 25,000 parts. It took about 25 minutes.

There's no doubt that the Pervasive tool is very fast. The trouble with the
tool is that it bypasses all business logic. So if you're not careful, you
can mess up your database. I believe that more than one person on this list
ended up with NULL fields that caused trouble later on - and that was even
after using the templates that Epicor had sold them.

That's not to say that a quality issue in the business object won't cause
trouble too but it will catch more errors.

Mark W.
Hello,
We have several parts that need to be imported into vantage (17000) . We are
doing it Via SC using a work flow. It calls the PartServices webservice we
done the connections and it works ok. Except that at the rate its going 1-5
seconds per part. It would take several days if not weeks to get these on
there. I thought it was SC being slow so we wrote our own procedure and
interact directly with the web services using WSE 3 and C# but it takes
about the same time to do the imports. Is this normal? If not then would the
problem be on IIS or the App server. The system seems to degrade overtime as
we import more and more parts.


Any ideas would be extremely appreciated

Thanks


Sincerely
Jose C Gomez
http://www.josecgomez.com

FYI
Microsoft and AOL won't give you money for forwarding an email.
The little girl named ____ is NOT dying of cancer.
And you will NOT die or have bad luck if you don't forward a message.


[Non-text portions of this message have been removed]
Wouldn't 17,000 take less than a day at that rate? Do you mean 170,000?

----- Original Message -----
From: Jose Gomez
To: vantage@yahoogroups.com
Sent: Monday, February 09, 2009 2:26 PM
Subject: [Vantage] Part Import very Slow


Hello,
We have several parts that need to be imported into vantage (17000) . We are
doing it Via SC using a work flow. It calls the PartServices webservice we
done the connections and it works ok. Except that at the rate its going 1-5
seconds per part. It would take several days if not weeks to get these on
there. I thought it was SC being slow so we wrote our own procedure and
interact directly with the web services using WSE 3 and C# but it takes
about the same time to do the imports. Is this normal? If not then would the
problem be on IIS or the App server. The system seems to degrade overtime as
we import more and more parts.

Any ideas would be extremely appreciated

Thanks

Sincerely
Jose C Gomez
http://www.josecgomez.com

FYI
Microsoft and AOL won't give you money for forwarding an email.
The little girl named ____ is NOT dying of cancer.
And you will NOT die or have bad luck if you don't forward a message.

[Non-text portions of this message have been removed]




[Non-text portions of this message have been removed]
1000-2000 parts/hour is fairly typical. The rate-limiter are the web
services - there's just a lot of overhead involved with the protocol
(SOAP). Service Connect will process things as quickly as the web
services will turn them around.



Epicor's position has consistently been with us that the web services
are slow but included with the product. If you want high-performance
data imports then you need to buy Pervasive. I have no argument with
that model.



You could easily break up your data import into multiple sub-files and
submit them in parallel. That should give you better throughput. I
imported 2347 parts this morning though and it took a couple of hours.



-bws



--

Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix

bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Jose Gomez
Sent: Monday, February 09, 2009 3:27 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Part Import very Slow



Hello,
We have several parts that need to be imported into vantage (17000) . We
are
doing it Via SC using a work flow. It calls the PartServices webservice
we
done the connections and it works ok. Except that at the rate its going
1-5
seconds per part. It would take several days if not weeks to get these
on
there. I thought it was SC being slow so we wrote our own procedure and
interact directly with the web services using WSE 3 and C# but it takes
about the same time to do the imports. Is this normal? If not then would
the
problem be on IIS or the App server. The system seems to degrade
overtime as
we import more and more parts.

Any ideas would be extremely appreciated

Thanks

Sincerely
Jose C Gomez
http://www.josecgomez.com

FYI
Microsoft and AOL won't give you money for forwarding an email.
The little girl named ____ is NOT dying of cancer.
And you will NOT die or have bad luck if you don't forward a message.

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
1-5 seconds per part is normal.

I just imported 45,000 parts that way over New Years weekend. It took 3
days for the import in 2,000-part sets. Painful and frustrating.

I did an import directly into SQL and I did 1,000+ per minute.

And yes, you will need to restart Service Connect services every 10,000
parts or so. I cleared my Service Connect messages/logs every 2000 part
set I imported.



-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Jose Gomez
Sent: Monday, February 09, 2009 3:27 PM
To: vantage@yahoogroups.com
Subject: [Vantage] Part Import very Slow

Hello,
We have several parts that need to be imported into vantage (17000) . We
are
doing it Via SC using a work flow. It calls the PartServices webservice
we
done the connections and it works ok. Except that at the rate its going
1-5
seconds per part. It would take several days if not weeks to get these
on
there. I thought it was SC being slow so we wrote our own procedure and
interact directly with the web services using WSE 3 and C# but it takes
about the same time to do the imports. Is this normal? If not then would
the
problem be on IIS or the App server. The system seems to degrade
overtime as
we import more and more parts.


Any ideas would be extremely appreciated

Thanks


Sincerely
Jose C Gomez
http://www.josecgomez.com

FYI
Microsoft and AOL won't give you money for forwarding an email.
The little girl named ____ is NOT dying of cancer.
And you will NOT die or have bad luck if you don't forward a message.


[Non-text portions of this message have been removed]



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
How lovely importing all our inventory will take weeks at this rate.
Thanks for your input.

Sincerely
Jose C Gomez
http://www.josecgomez.com

FYI
Microsoft and AOL won't give you money for forwarding an email.
The little girl named ____ is NOT dying of cancer.
And you will NOT die or have bad luck if you don't forward a message.




On Mon, Feb 9, 2009 at 5:16 PM, Vic Drecchio <vic.drecchio@...>wrote:

> 1-5 seconds per part is normal.
>
> I just imported 45,000 parts that way over New Years weekend. It took 3
> days for the import in 2,000-part sets. Painful and frustrating.
>
> I did an import directly into SQL and I did 1,000+ per minute.
>
> And yes, you will need to restart Service Connect services every 10,000
> parts or so. I cleared my Service Connect messages/logs every 2000 part
> set I imported.
>
>
> -----Original Message-----
> From: vantage@yahoogroups.com <vantage%40yahoogroups.com> [mailto:
> vantage@yahoogroups.com <vantage%40yahoogroups.com>] On Behalf
> Of Jose Gomez
> Sent: Monday, February 09, 2009 3:27 PM
> To: vantage@yahoogroups.com <vantage%40yahoogroups.com>
> Subject: [Vantage] Part Import very Slow
>
> Hello,
> We have several parts that need to be imported into vantage (17000) . We
> are
> doing it Via SC using a work flow. It calls the PartServices webservice
> we
> done the connections and it works ok. Except that at the rate its going
> 1-5
> seconds per part. It would take several days if not weeks to get these
> on
> there. I thought it was SC being slow so we wrote our own procedure and
> interact directly with the web services using WSE 3 and C# but it takes
> about the same time to do the imports. Is this normal? If not then would
> the
> problem be on IIS or the App server. The system seems to degrade
> overtime as
> we import more and more parts.
>
> Any ideas would be extremely appreciated
>
> Thanks
>
> Sincerely
> Jose C Gomez
> http://www.josecgomez.com
>
> FYI
> Microsoft and AOL won't give you money for forwarding an email.
> The little girl named ____ is NOT dying of cancer.
> And you will NOT die or have bad luck if you don't forward a message.
>
> [Non-text portions of this message have been removed]
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
> have already linked your email address to a yahoo id to enable access. )
> (1) To access the Files Section of our Yahoo!Group for Report Builder
> and Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>
>
>


[Non-text portions of this message have been removed]
I hear you. If there is any silver lining to this scenario, at least
you don't need exclusive access to the database. Meaning you can do it
during normal business hours just fine.

-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Jose Gomez
Sent: Monday, February 09, 2009 5:21 PM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Part Import very Slow

How lovely importing all our inventory will take weeks at this rate.
Thanks for your input.

Sincerely
Jose C Gomez
http://www.josecgomez.com

FYI
Microsoft and AOL won't give you money for forwarding an email.
The little girl named ____ is NOT dying of cancer.
And you will NOT die or have bad luck if you don't forward a message.




On Mon, Feb 9, 2009 at 5:16 PM, Vic Drecchio
<vic.drecchio@...>wrote:

> 1-5 seconds per part is normal.
>
> I just imported 45,000 parts that way over New Years weekend. It took
3
> days for the import in 2,000-part sets. Painful and frustrating.
>
> I did an import directly into SQL and I did 1,000+ per minute.
>
> And yes, you will need to restart Service Connect services every
10,000
> parts or so. I cleared my Service Connect messages/logs every 2000
part
> set I imported.
>
>
> -----Original Message-----
> From: vantage@yahoogroups.com <vantage%40yahoogroups.com> [mailto:
> vantage@yahoogroups.com <vantage%40yahoogroups.com>] On Behalf
> Of Jose Gomez
> Sent: Monday, February 09, 2009 3:27 PM
> To: vantage@yahoogroups.com <vantage%40yahoogroups.com>
> Subject: [Vantage] Part Import very Slow
>
> Hello,
> We have several parts that need to be imported into vantage (17000) .
We
> are
> doing it Via SC using a work flow. It calls the PartServices
webservice
> we
> done the connections and it works ok. Except that at the rate its
going
> 1-5
> seconds per part. It would take several days if not weeks to get these
> on
> there. I thought it was SC being slow so we wrote our own procedure
and
> interact directly with the web services using WSE 3 and C# but it
takes
> about the same time to do the imports. Is this normal? If not then
would
> the
> problem be on IIS or the App server. The system seems to degrade
> overtime as
> we import more and more parts.
>
> Any ideas would be extremely appreciated
>
> Thanks
>
> Sincerely
> Jose C Gomez
> http://www.josecgomez.com
>
> FYI
> Microsoft and AOL won't give you money for forwarding an email.
> The little girl named ____ is NOT dying of cancer.
> And you will NOT die or have bad luck if you don't forward a message.
>
> [Non-text portions of this message have been removed]
>
> ------------------------------------
>
> Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
> have already linked your email address to a yahoo id to enable access.
)
> (1) To access the Files Section of our Yahoo!Group for Report Builder
> and Crystal Reports and other 'goodies', please goto:
> http://groups.yahoo.com/group/vantage/files/.
> (2) To search through old msg's goto:
> http://groups.yahoo.com/group/vantage/messages
> (3) To view links to Vendors that provide Vantage services goto:
> http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
>
>
>


[Non-text portions of this message have been removed]



------------------------------------

Useful links for the Yahoo!Groups Vantage Board are: ( Note: You must
have already linked your email address to a yahoo id to enable access. )
(1) To access the Files Section of our Yahoo!Group for Report Builder
and Crystal Reports and other 'goodies', please goto:
http://groups.yahoo.com/group/vantage/files/.
(2) To search through old msg's goto:
http://groups.yahoo.com/group/vantage/messages
(3) To view links to Vendors that provide Vantage services goto:
http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
> 1000-2000 parts/hour is fairly typical. The rate-limiter are the web
> services - there's just a lot of overhead involved with the protocol
> (SOAP). Service Connect will process things as quickly as the web
> services will turn them around.

There is a third option and that is adding your parts using the business
objects directly using C# or VB.Net. This is how I did it. You eliminate the
all of that marshalling and un-marshalling overhead of SOAP. You can get the
idea from a previous thread:

http://tech.groups.yahoo.com/group/vantage/message/60826

Mark W.
Mark, would you be willing to post a more complete example somewhere?



I'm well-versed in C#/.NET, and I'm wondering how one gets started
with programming against the .NET APIs. Did you buy the SDK or is there
a cheaper, simpler way to consume these without having to become a total
expert?



-bws



--

Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
Picometrix

bspolarich@... ~ 734-864-5618 ~
www.advancedphotonix.com



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Monday, February 09, 2009 9:13 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Part Import very Slow



> 1000-2000 parts/hour is fairly typical. The rate-limiter are the web
> services - there's just a lot of overhead involved with the protocol
> (SOAP). Service Connect will process things as quickly as the web
> services will turn them around.

There is a third option and that is adding your parts using the business
objects directly using C# or VB.Net. This is how I did it. You eliminate
the
all of that marshalling and un-marshalling overhead of SOAP. You can get
the
idea from a previous thread:

http://tech.groups.yahoo.com/group/vantage/message/60826

Mark W.





[Non-text portions of this message have been removed]
I would like that also a more in depth example if you are willing we do a
lot with C# .NET here and this would be awesome to implement and it seems it
would cut down our import time tremendously.

Thnaks
Sincerely
Jose C Gomez
http://www.josecgomez.com

FYI
Microsoft and AOL won't give you money for forwarding an email.
The little girl named ____ is NOT dying of cancer.
And you will NOT die or have bad luck if you don't forward a message.




On Tue, Feb 10, 2009 at 9:14 AM, Brian W. Spolarich <
bspolarich@...> wrote:

> Mark, would you be willing to post a more complete example somewhere?
>
> I'm well-versed in C#/.NET, and I'm wondering how one gets started
> with programming against the .NET APIs. Did you buy the SDK or is there
> a cheaper, simpler way to consume these without having to become a total
> expert?
>
>
> -bws
>
> --
>
> Brian W. Spolarich ~ Manager, Information Services ~ Advanced Photonix /
> Picometrix
>
> bspolarich@... <bspolarich%40advancedphotonix.com> ~
> 734-864-5618 ~
> www.advancedphotonix.com
>
> From: vantage@yahoogroups.com <vantage%40yahoogroups.com> [mailto:
> vantage@yahoogroups.com <vantage%40yahoogroups.com>] On Behalf
> Of Mark Wonsil
> Sent: Monday, February 09, 2009 9:13 PM
> To: vantage@yahoogroups.com <vantage%40yahoogroups.com>
> Subject: RE: [Vantage] Part Import very Slow
>
> > 1000-2000 parts/hour is fairly typical. The rate-limiter are the web
> > services - there's just a lot of overhead involved with the protocol
> > (SOAP). Service Connect will process things as quickly as the web
> > services will turn them around.
>
> There is a third option and that is adding your parts using the business
> objects directly using C# or VB.Net. This is how I did it. You eliminate
> the
> all of that marshalling and un-marshalling overhead of SOAP. You can get
> the
> idea from a previous thread:
>
> http://tech.groups.yahoo.com/group/vantage/message/60826
>
> Mark W.
>
> [Non-text portions of this message have been removed]
>
>
>


[Non-text portions of this message have been removed]
Jose after Brian,

> I would like that also a more in depth example if you are willing we do a
> lot with C# .NET here and this would be awesome to implement and it seems
> it would cut down our import time tremendously.
>
> > Mark, would you be willing to post a more complete example somewhere?
> >
> > I'm well-versed in C#/.NET, and I'm wondering how one gets started
> > with programming against the .NET APIs. Did you buy the SDK or is there
> > a cheaper, simpler way to consume these without having to become a total
> > expert?

Really, all I did was to open a Project (you can even do this is the Express
Editions of VS for C# or VB.Net) and add the references to the business
objects that I wanted to work with: Epicor.Mfg.IF.Part.dll,
Epicor.Mfg.AD.Part.dll, etc.

Next, I did the same kind of tracing analysis that you would do for SC to
see the business objects and parameters used. The calls should be similar to
SC.

Basically, you consume a full license and log in (Session object) as if you
were the UI and the BOs don't really know that you're not the UI (or it
shouldn't if the sales rep was telling the truth about the separation of the
UI to the business logic. The code will (or should anyway) throw exceptions
if you do anything wrong.

Adding parts with plant and rev records is quite easy. OTOH, methods of
manufacturing are a real b_tch since you have to control the Engineering WB
business object.

I have to run out for a bit but ask if you have any questions about the
previous example post
(http://tech.groups.yahoo.com/group/vantage/message/60826) or if there's
something else that you're trying to do.

Mark W.
Thanks Mark,
Do you need the SDK for this to work? We didn't purchase that and I am not
sure if it would work without it.

Thanks again.

Sincerely
Jose C Gomez
http://www.josecgomez.com

FYI
Microsoft and AOL won't give you money for forwarding an email.
The little girl named ____ is NOT dying of cancer.
And you will NOT die or have bad luck if you don't forward a message.




On Tue, Feb 10, 2009 at 10:15 AM, Mark Wonsil <mark_wonsil@...> wrote:

> Jose after Brian,
>
>
> > I would like that also a more in depth example if you are willing we do a
> > lot with C# .NET here and this would be awesome to implement and it seems
> > it would cut down our import time tremendously.
> >
> > > Mark, would you be willing to post a more complete example somewhere?
> > >
> > > I'm well-versed in C#/.NET, and I'm wondering how one gets started
> > > with programming against the .NET APIs. Did you buy the SDK or is there
> > > a cheaper, simpler way to consume these without having to become a
> total
> > > expert?
>
> Really, all I did was to open a Project (you can even do this is the
> Express
> Editions of VS for C# or VB.Net) and add the references to the business
> objects that I wanted to work with: Epicor.Mfg.IF.Part.dll,
> Epicor.Mfg.AD.Part.dll, etc.
>
> Next, I did the same kind of tracing analysis that you would do for SC to
> see the business objects and parameters used. The calls should be similar
> to
> SC.
>
> Basically, you consume a full license and log in (Session object) as if you
> were the UI and the BOs don't really know that you're not the UI (or it
> shouldn't if the sales rep was telling the truth about the separation of
> the
> UI to the business logic. The code will (or should anyway) throw exceptions
> if you do anything wrong.
>
> Adding parts with plant and rev records is quite easy. OTOH, methods of
> manufacturing are a real b_tch since you have to control the Engineering WB
> business object.
>
> I have to run out for a bit but ask if you have any questions about the
> previous example post
> (http://tech.groups.yahoo.com/group/vantage/message/60826) or if there's
> something else that you're trying to do.
>
> Mark W.
>
>
>


[Non-text portions of this message have been removed]
Hey Mark,

We are having a little difficulty in finding the object
"Epicor.Mfg.BO.PartDataSet". Can you tell us where you got that
from???



--Matt





From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf
Of Mark Wonsil
Sent: Monday, February 09, 2009 8:13 PM
To: vantage@yahoogroups.com
Subject: RE: [Vantage] Part Import very Slow



> 1000-2000 parts/hour is fairly typical. The rate-limiter are the web
> services - there's just a lot of overhead involved with the protocol
> (SOAP). Service Connect will process things as quickly as the web
> services will turn them around.

There is a third option and that is adding your parts using the business
objects directly using C# or VB.Net. This is how I did it. You eliminate
the
all of that marshalling and un-marshalling overhead of SOAP. You can get
the
idea from a previous thread:

http://tech.groups.yahoo.com/group/vantage/message/60826

Mark W.





[Non-text portions of this message have been removed]
We use it for all out integration needs although it is very slow and cranky
LoL.



Sincerely
Jose C Gomez
http://www.josecgomez.com

FYI
Microsoft and AOL won't give you money for forwarding an email.
The little girl named ____ is NOT dying of cancer.
And you will NOT die or have bad luck if you don't forward a message.




On Tue, Feb 10, 2009 at 11:27 AM, Bruce Ordway <cooner_55421@...>wrote:

> Hi,
>
> We have a Progress db and used Pervasive and ODBC to import about
> 25,000 parts. It took about 25 minutes.
>
> We also have Service Connect, but I have not learnded to use it yet.
> I have Pervasive & there has been no need for anything else yet.
>
> I have been hearing more about Service Connect though & am wondering
> if I should start working with it. Any suggestions for somebody just
> starting out with it? What are some of your favorite things to use it
> for?
>
> Thanks,
>
> Bruce
>
> --- In vantage@yahoogroups.com <vantage%40yahoogroups.com>, "Vic Drecchio"
> <vic.drecchio@...>
> wrote:
>
> >
> > 1-5 seconds per part is normal.
> >
> > I just imported 45,000 parts that way over New Years weekend. It
> took 3
> > days for the import in 2,000-part sets. Painful and frustrating.
> >
> > I did an import directly into SQL and I did 1,000+ per minute.
> >
> > And yes, you will need to restart Service Connect services every
> 10,000
> > parts or so. I cleared my Service Connect messages/logs every 2000
> part
> > set I imported.
> >
> >
> >
> > -----Original Message-----
> > From: vantage@yahoogroups.com <vantage%40yahoogroups.com> [mailto:
> vantage@yahoogroups.com <vantage%40yahoogroups.com>] On
> Behalf
> > Of Jose Gomez
> > Sent: Monday, February 09, 2009 3:27 PM
> > To: vantage@yahoogroups.com <vantage%40yahoogroups.com>
> > Subject: [Vantage] Part Import very Slow
> >
> > Hello,
> > We have several parts that need to be imported into vantage
> (17000) . We
> > are
> > doing it Via SC using a work flow. It calls the PartServices
> webservice
> > we
> > done the connections and it works ok. Except that at the rate its
> going
> > 1-5
> > seconds per part. It would take several days if not weeks to get
> these
> > on
> > there. I thought it was SC being slow so we wrote our own procedure
> and
> > interact directly with the web services using WSE 3 and C# but it
> takes
> > about the same time to do the imports. Is this normal? If not then
> would
> > the
> > problem be on IIS or the App server. The system seems to degrade
> > overtime as
> > we import more and more parts.
> >
> >
> > Any ideas would be extremely appreciated
> >
> > Thanks
> >
> >
> > Sincerely
> > Jose C Gomez
> > http://www.josecgomez.com
> >
> > FYI
> > Microsoft and AOL won't give you money for forwarding an email.
> > The little girl named ____ is NOT dying of cancer.
> > And you will NOT die or have bad luck if you don't forward a
> message.
> >
> >
> > [Non-text portions of this message have been removed]
> >
> >
> >
> > ------------------------------------
> >
> > Useful links for the Yahoo!Groups Vantage Board are: ( Note: You
> must
> > have already linked your email address to a yahoo id to enable
> access. )
> > (1) To access the Files Section of our Yahoo!Group for Report
> Builder
> > and Crystal Reports and other 'goodies', please goto:
> > http://groups.yahoo.com/group/vantage/files/.
> > (2) To search through old msg's goto:
> > http://groups.yahoo.com/group/vantage/messages
> > (3) To view links to Vendors that provide Vantage services goto:
> > http://groups.yahoo.com/group/vantage/linksYahoo! Groups Links
> >
>
>
>


[Non-text portions of this message have been removed]
> We are having a little difficulty in finding the object
> "Epicor.Mfg.BO.PartDataSet". Can you tell us where you got that
> from???

Make sure that you add a reference to Epicor.Mfg.BO.Part.dll (you should
have the Vantage/Epicor client on your machine and browse to the client
folder) It's in there. Once you add the reference to the project, you can
use the Object Browser to see the properties and methods and even *some*
documentation!

Mark W.