data error

[andersun]

modeling equipment and on half of the vessels I model I now receive this error message. see attachment. where do I look to correct this? I can't locate a 3d nozzle tag in data manager.

[Bingo]

Before add nozzle,you must set the line_number.I guess it is reason why error happened.

[andersun]

I deleted the component and save the drawing. Exited and re open the drawing. I then created an nozzle using the same tag as before. I insured that I picked a line number and place the nozzle on the vessel. All went good I received no error when placing the nozzle but the error returned when I reopened the drawing.

[clarabie]

Okay, the error message is indicating that the field TAG in the NOZZLE3D table in the drawing database (assuming you are using Access) is empty for that component. We have had many similar issues with equipment components but I can't answer why you were able to delete and replace the nozzle with no error, then get an error upon reopening the drawing without more information, like, do you use document manager/vision to open your drawings, etc. Let me know if this is still an issue

[andersun]

yes the problem has not cleared up. As far as opening the drawing I'm using autocad to open the drawing from the file pulldown. The drawings created within the project are fine, and only some of the imported drawings have this problem. Also on some effected drawings only a couple nozzles are effected. I did not receive any errors on importing the files. The data base shows the correct information is in the fields for the nozzles, as long as I'm looking at the correct data base.

[clarabie]

what's this about imported drawings? Not mentioned before..

that leads to more questions - were these drawings imported from a different project name? or same project name (maybe from another office)?

Are you using access, msde or sql?

[andersun]

Oh Yea they were imported, the imported drawings were done in access and have a different project name. the project we need them in is running on a SQL. me thought is there was a hiccup in some of the data transfer but I dont know where th go to correct it. is this some thing were I need to export the effected drawing back to the project and correct the database error there and then re-import them in the the project?

[clarabie]

First of all, I'm not sure how you accomplished importing an Access project into a SQL project through Bentley - It isn't supposed to be able to be done.

Secondly, the import/export utility was only designed to work with projects with the same name. Last year we had a project roll over into a nearly identical project, so I used the import/export utility in PA. Discovered many problems, so I used trial and error to try to correct the problem. Unfortunately, the only way to correct it is to have the original projdata.mdb file from the same date as the original export. Here are the steps I took to successfully export/import from one project name to a different project...

1.The model(s) first must be exported from the old project using the export utility in the Project Administrator.

2.The export package is then imported to the new project, also through the Project Administrator. (At this point Bentley says “quit” – not true)

3.Open AutoPLANT and load piping, selecting the new project.

4.May get a dialog box saying something like “this is a model from another project, do you want to make it part of this project”. Select “yes”.

5.Do a SAVEAS and save as a new drawing name (example: 1884X01 to 1963X01). If maintaining original drawing name, then you will have to do SAVEAS twice – once to a temporary name such as 1884X01a, deleting 1884X01 after 1st SAVEAS, then doing another SAVEAS the original drawing name.

6.Use Document Manager to delete the model(s) that were originally imported into the project.


Without doing the SAVEAS, the piping components of the imported model never make it to the project database, meaning that you can’t run isos by line number. Additionally, line number relationships are also lost to the project and if you edit components, all info except line number is present (line number is not saved with the drawing database, but resides in the projectdata.mdb).

Lots of headaches till I tried it this way. Use this same procedure if a model somehow loses connectivity with the project.


I don't know if this will work the same with a sql project...
Good Luck!!!

[Bingo]

Good method,thanks for clarabie's help.
Before,i do not know the step of "SAVEAS",i just export modeling from a project,then import it to a new project.So many problem happened.
I will try this method.thank you very much.

[andersun]

Clarabie,

We still have a bit of a disconnect with the problem, But what you last posted gave me the help I needed. I never posted it but I only have equipment in the project no piping. I was able to delete the vessel with problems and just quickly redraw them with out errors. Once you pointed me to the project object management tool all was good. thank you for the help.