Page 1 of 1

database useage issues

Posted: Tue Sep 13, 2011 11:46 am
by MikeM
Hi team - I seem to be having an issue with version 11, it seems to be picking certain assemblies out of the database that are not even turned on for use. This is mainly seen with elbow assemblies that I use for PVC Submain riser pipe to poly pipe lateral connections.

Some of our customers want something different from my typical riser assembly. Therefore I generally have several different types of risers for the same connection type/size with the minor alternations that are preferred. i.e. a ball valve or a pipe clamp, some are actually rather complex. Now I leave these custom risers turned off in the database until I work on a project for these customers, in which I turn off the "typical" and turn on the custom riser.

Prior to version 11 it worked well, now it seems the computer selection of fittings pulls the typical riser even when they are turned off. Sometimes I can get it work, but honestly I don't know how it gets on the right track. Is there some kind of delay in getting Irricad to notice assembly useage changes in the database? Restarting Irricad and the database do not seem to change anything. Also it seems to lose association more frequently with pipes and items that are turned on in the database but are showing up with "green" text in the design when inspecting said pipe or fittings. Any Ideas?

I am wondering if it has anything to do with the database and the irricad program being on different drives? (has been for years) but a lot seems to have changed with the database in version 11, thought there could be a conflict.

Thanks much!

Mike

Re: database useage issues

Posted: Wed Sep 14, 2011 3:44 am
by MikeM
Simple solution...it seems when you leave the usage code empty (which I thought was the same as "N"), the assembly can still be used. Changed it to "N" and it was omitted from the selection process.

Re: database useage issues

Posted: Wed Sep 14, 2011 8:36 am
by Dan Crosby
Mike, "blank" is supposed to be equivalent to "N", but we did have a problem with space padding, which should be fixed in the next patch. All going to plan, that should be out this week or early next week.