:-)
Jose's correct, if they ever find out you've done that, they may deny
support.
Ernie, I don't know enough about these tables and the RoHS process to say it
can't be done. But ultimately, I believe you can simulate anything in the
SQL db that the UI performs via TSQL code.
Sounds like you've done your due diligence and continue to further
research... that's good. I'd do it in your TEST db first. Play with the
system for a couple weeks and let "real users" also log into TEST to try and
validate or break. Not sure how you've done your research and testing, but
one of the things I do is run a query to give me a rowcount of all tables in
the db. Then I do "it" from the UI. "It" may be entering a new Job or
Part; or in your case, whatever it is to do with RoHS. Then do another
snapshot of all the tables. See what tables have changed. Also SQL
Profiler is valuable.
When you're done testing, test some more.
If you decide to pull the trigger and roll with this idea, leave yourself
breadcrumbs in the tables you update "just in case" you need to undo
something. By "breadcrumbs" I mean, utilize a UD field like Number20 in the
table you're updating or inserting. I set mine to 999 or something like
that just to simply flag that record as something I modified. When I
update/modify field values (versus inserting), I may also set another UD
field with the original value just in case I need to undo. Later on down
the road, you can clear out your UD flags or just leave them there
indefinitely.
Don't do this if you're the least bit frightened. I'm not sure what your
role and responsibility is in your organization, but this could lead to a
dire catastrophe if done wrong. I cannot count the number of times I've had
to perform surgery on db's for various companies just because it was easy to
modify the db from Excel or something.
Good luck.
-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Jose Gomez
Sent: Wednesday, November 14, 2012 10:25 AM
To: Vantage
Subject: Re: [Vantage] DB Update?
Your Support contract would at that point be null and void should something
blow up. You can write a tool to import this using the BO's which would be
supported.
PS: Vic look away do not answer this question ok? lol
*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>
*Quis custodiet ipsos custodes?*
On Wed, Nov 14, 2012 at 10:20 AM, Elizabeth
<gracefulthreads@...>wrote:
------------------------------------
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
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2441/5394 - Release Date: 11/14/12
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2441/5394 - Release Date: 11/14/12
Jose's correct, if they ever find out you've done that, they may deny
support.
Ernie, I don't know enough about these tables and the RoHS process to say it
can't be done. But ultimately, I believe you can simulate anything in the
SQL db that the UI performs via TSQL code.
Sounds like you've done your due diligence and continue to further
research... that's good. I'd do it in your TEST db first. Play with the
system for a couple weeks and let "real users" also log into TEST to try and
validate or break. Not sure how you've done your research and testing, but
one of the things I do is run a query to give me a rowcount of all tables in
the db. Then I do "it" from the UI. "It" may be entering a new Job or
Part; or in your case, whatever it is to do with RoHS. Then do another
snapshot of all the tables. See what tables have changed. Also SQL
Profiler is valuable.
When you're done testing, test some more.
If you decide to pull the trigger and roll with this idea, leave yourself
breadcrumbs in the tables you update "just in case" you need to undo
something. By "breadcrumbs" I mean, utilize a UD field like Number20 in the
table you're updating or inserting. I set mine to 999 or something like
that just to simply flag that record as something I modified. When I
update/modify field values (versus inserting), I may also set another UD
field with the original value just in case I need to undo. Later on down
the road, you can clear out your UD flags or just leave them there
indefinitely.
Don't do this if you're the least bit frightened. I'm not sure what your
role and responsibility is in your organization, but this could lead to a
dire catastrophe if done wrong. I cannot count the number of times I've had
to perform surgery on db's for various companies just because it was easy to
modify the db from Excel or something.
Good luck.
-----Original Message-----
From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Jose Gomez
Sent: Wednesday, November 14, 2012 10:25 AM
To: Vantage
Subject: Re: [Vantage] DB Update?
Your Support contract would at that point be null and void should something
blow up. You can write a tool to import this using the BO's which would be
supported.
PS: Vic look away do not answer this question ok? lol
*Jose C Gomez*
*Software Engineer*
*
*
*
*T: 904.469.1524 mobile
E: jose@...
http://www.josecgomez.com
<http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
<http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
<http://www.josecgomez.com/professional-resume/>
<http://www.josecgomez.com/feed/>
<http://www.usdoingstuff.com>
*Quis custodiet ipsos custodes?*
On Wed, Nov 14, 2012 at 10:20 AM, Elizabeth
<gracefulthreads@...>wrote:
> **direct SQL upload?
>
>
> We're starting to get slammed with RoHS requests and would LOVE to be
> able to do a mass upload of data. Unfortunately, the
> PartMtlRestriction and PartMtlRestrictSubst tables are not accessible
> via DMT. Since they seem to be pretty static (the RoHS roll-up
> processes seems to CALL data from them for calculations, not CREATE
> data in them), does anyone know of a reason that would preclude doing a
>[Non-text portions of this message have been removed]
> There are also the Substance, RestrictionType and RestructionSubstance
> tables, and I need to do more testing to find out all the
> relationships and requirements (mostly what has to be updated in which
> order), but once I get that nailed down what OTHER damage would I do?
>
> Ernie Lowell
> Diba Industries
>
>
>
------------------------------------
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
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2441/5394 - Release Date: 11/14/12
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 2012.0.2221 / Virus Database: 2441/5394 - Release Date: 11/14/12