Run Delete

[HybridAWD]

It's official, I want a run delete option when you CATT on lines and look at the process tab.

This would be a huge help when there is 2+ To's or 2+ From's. Seems like it should be that hard to incorporate. This would be a great asset! The End.

[Aplant Monkey]

I totally agree that this option would be huge if it were available and it linked back to the process table to get rid of multiple T/F's this has been on my hit list for a long time.... good call

[dave]

sounds great. Would this be a reporting solution?

[Aplant Monkey]

not sure this would be a solution but it certainly would help with the clean up of the DB when trying to run various reports.

[HybridAWD]

Yeah, it would help so much. I might be able to get our Software Engineer to mess with it and see if he could come up with something. But who knows.

[dave]

yep. In the interim, just create a query (view) that groups by "first of" and that be the data source of your report. :)

[HybridAWD]

Dave, elaborate... i think you've been drinking or maybe lack of sleep.

[dave]

Nick, create a new view in a dummy project with some data and paste this in the SQL view

SELECT PROCESS.KEYTAG, First(TAG_REG.TAG_NO) AS [PROCESS TAG], TAG_REG.PROJ_STAT AS STATUS, PROCESS.PSERV AS SERVICE, PROCESS.PSPEC_NOM AS [NOMINAL SPEC], PROCESS.PSZ_NOM AS [NOMINAL SIZE], PROCESS.PMATL AS [STRESS RELIEF], PROCESS.POPP_NOM AS [NOMINAL OP PRESS], PROCESS.POPT_NOM AS [NOMINAL OP TEMP], PROCESS.PTESTP AS [TEST PRESS], PROCESS.PINS AS INSULATION, PROCESS.PTRC AS [TRACE HEATING], PROCESS.PPAINT AS PAINT, PROCESS.PDWGPIPE AS [PIPING DRG], PIPE_RUN.PAREA AS AREA, First(PIPE_RUN.RUN_NAME) AS [RUN NO], PIPE_RUN.PSZ AS [RUN SIZE], PIPE_RUN.PSPEC AS [RUN SPEC], PIPE_RUN.PCLASS AS [RUN CLASS], NOZZLE.PDIRECT AS [FLOW DIRECTION], TAG_REG_1.TAG_NO AS [EQUIP TAG], TAG_REG_1.TAG_TYPE AS [EQUIP TYPE], EQUIP.EDESC AS [EQUIP DESCRIPTION], TAG_REG_2.TAG_NO AS [NOZZ TAG], PIPE_RUN.PSTREAM AS STREAM, PIPE_RUN.PFLOW AS [FLOW RATE], PIPE_RUN.POPP AS [OP PRESS], PIPE_RUN.POPT AS [OP TEMP], PIPE_RUN.PINT1 AS [PROCESS TYPE], DOC_REG.DOC_NAME AS [PID NO], PROCESS.COMP_ID, TAG_REG.TAG_TYPE, TAG_REG.TAG_NO
FROM ((((((TAG_REG RIGHT JOIN ((NOZZLE RIGHT JOIN PIPE_RUN ON NOZZLE.NLINE = PIPE_RUN.KEYTAG) RIGHT JOIN PROCESS ON PIPE_RUN.LINE_ID = PROCESS.KEYTAG) ON TAG_REG.KEYTAG = PROCESS.KEYTAG) LEFT JOIN EQUIP ON NOZZLE.NEQUIP = EQUIP.KEYTAG) LEFT JOIN TAG_REG AS TAG_REG_1 ON NOZZLE.NEQUIP = TAG_REG_1.KEYTAG) LEFT JOIN TAG_REG AS TAG_REG_2 ON NOZZLE.KEYTAG = TAG_REG_2.KEYTAG) LEFT JOIN KEY_LINK ON EQUIP.KEYTAG = KEY_LINK.KEYTAG) LEFT JOIN EQP_LNK ON KEY_LINK.LINK_ID = EQP_LNK.LINK_ID) LEFT JOIN DOC_REG ON EQP_LNK.DWG_NAME = DOC_REG.DOC_ID
GROUP BY PROCESS.KEYTAG, TAG_REG.PROJ_STAT, PROCESS.PSERV, PROCESS.PSPEC_NOM, PROCESS.PSZ_NOM, PROCESS.PMATL, PROCESS.POPP_NOM, PROCESS.POPT_NOM, PROCESS.PTESTP, PROCESS.PINS, PROCESS.PTRC, PROCESS.PPAINT, PROCESS.PDWGPIPE, PIPE_RUN.PAREA, PIPE_RUN.PSZ, PIPE_RUN.PSPEC, PIPE_RUN.PCLASS, NOZZLE.PDIRECT, TAG_REG_1.TAG_NO, TAG_REG_1.TAG_TYPE, EQUIP.EDESC, TAG_REG_2.TAG_NO, PIPE_RUN.PSTREAM, PIPE_RUN.PFLOW, PIPE_RUN.POPP, PIPE_RUN.POPT, PIPE_RUN.PINT1, DOC_REG.DOC_NAME, PROCESS.COMP_ID, TAG_REG.TAG_TYPE, TAG_REG.TAG_NO
ORDER BY First(TAG_REG.TAG_NO), First(PIPE_RUN.RUN_NAME), NOZZLE.PDIRECT;

I use this model for line lists, spec items, etc..

*burp*

[HybridAWD]

ill check this out tomorrow....


I guess we can eliminate lack of sleep now ;)

[dave]

no, lack of sleep is my vice. :)

[dave]

Nick, did you check out the view?

[HybridAWD]

yeah we tried it out. So what do you do with it? Do you delete from there?

With the Bentley generic list, it kinda shows the same thing, but not in view form like yours. Either way, your thing was pretty neat.

[dave]

you don't need to delete anything, there should only be one instance of each pipe run.

[HybridAWD]

you don't need to delete anything, there should only be one instance of each pipe run.

yeah that is what I thought it was for. We have this sweet online thing that out software engineer guy setup for us. It pulls from the Bentley DB and gives us all kinds of cool info, for example, duplicate tags numbers whether it's with lines, equipment, instruments. It also tells us if there isn't enough info on certain lines, such as no spec, service, insulation. Another feature is that it summarizes it all into 1 document. It's definitely very nice to have, then again, the engineers have access to look at it, and they are always questioning us on it. They like to bring up concerns we already know about. But overall, it makes our quality of work that much better.