First, thanks for the chuckle Michael. Of course, you realize that by
deleting rows off those other tables, that would mean there will be other
tables you need to delete from. Rather than publish the second level of
purges you need to go to, just see the list by running "Data Dictionary".
I agree with Mark on the first choice. I'd recommend, if you don't already
have it, getting DMT. It's a relatively inexpensive product, but you can
get that delete running in a matter of minutes. And, if there's part
transactions that exist - it rightfully won't delete the part.
Kevin Simon
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Mark Wonsil
Sent: Thursday, July 05, 2012 11:59 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Deleting all the parts in the database
Michael wrote:
need to delete the appropriate records from each of the following tables:
first choice is to just restore the database to a state before you did
the mass load. My second choice, if you really need to delete parts
and save other work, is to write a .Net program to use the business
objects to delete each part to ensure database integrity. It would be
a fairly easy program to write.
Mark W.
[Non-text portions of this message have been removed]
deleting rows off those other tables, that would mean there will be other
tables you need to delete from. Rather than publish the second level of
purges you need to go to, just see the list by running "Data Dictionary".
I agree with Mark on the first choice. I'd recommend, if you don't already
have it, getting DMT. It's a relatively inexpensive product, but you can
get that delete running in a matter of minutes. And, if there's part
transactions that exist - it rightfully won't delete the part.
Kevin Simon
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Mark Wonsil
Sent: Thursday, July 05, 2012 11:59 AM
To: vantage@yahoogroups.com
Subject: Re: [Vantage] Deleting all the parts in the database
Michael wrote:
> The following is a list of tables where it is possible for a part recordto exist. If you wish to insure that your purge is comprehensive you will
need to delete the appropriate records from each of the following tables:
> :...
>Michael and others are correct. SQL is not the way I would go. My
> Good Luck with your purge.
>
first choice is to just restore the database to a state before you did
the mass load. My second choice, if you really need to delete parts
and save other work, is to write a .Net program to use the business
objects to delete each part to ensure database integrity. It would be
a fairly easy program to write.
Mark W.
[Non-text portions of this message have been removed]