Block Manager

[gizmowiebe]

Hi There,
I'm trying to create a block manager using VBA. I'ts all working fine. But the thing is I would like to create a block manager witch users can fill in for themselves. So they can create different groups with different blocks in them.

I all must look something like this.

[Mounting Brackets] <=== Group name
F12-108-0 <=== Block name
F12-205-1

[Assembly Parts]
F11-202-0
F11-506-2

Is there a way that I can create this, the Group names and block names. And to do this so that I can be edited all the time.

Regards Wiebe

[TomD]

"gizmowiebe" <nospam@address.withheld> wrote in message
news:9319539.1102949277828.JavaMail.jive@jiveforum 2.autodesk.com...

Hi There,
I'm trying to create a block manager using VBA. I'ts all working fine. But
the thing is I would like to create a block manager witch users can fill in

for themselves. So they can create different groups with different blocks in
them.

I all must look something like this.

[Mounting Brackets] <=== Group name
F12-108-0 <=== Block name
F12-205-1

[Assembly Parts]
F11-202-0
F11-506-2

Is there a way that I can create this, the Group names and block names.
And to do this so that I can be edited all the time.

Of course, this depends on how, exactly, you have your libray configured.
If it is database driven, you can have a field for "Group Name", then with
SQL you can easily do a SELECT DISTINCT [Group Name] query, which would give
you all of your groups. Then, for each group, you can display the matching
blocks.

I've done this with an intranet web links page, as well. It does provide
plenty of flexibility, though it does leave more data control up to the
users.

HTH

[gizmowiebe]

I Havend driven the database yet. I'm looking for the best option. What do you think?

[TomD]

"gizmowiebe" <nospam@address.withheld> wrote in message
news:7122617.1102953692253.JavaMail.jive@jiveforum 2.autodesk.com...

I Havend driven the database yet. I'm looking for the best option. What do
you think?

Well, using a database gives you alot more control and more options, as far
as the interface is concerned. The data is all centralized and tends to be
much easier to control, since you are determining the users level of
involvement.

If you want something 'simpler', maybe a "blocks" folder, with a subfolder
for each group, then your manager could use FileSystemObject to iterate
through them, collecting the available symbols. The downside to this method
is that maintaining a description would be a little harder to control.

Please repost with your solution, when you're satisfied. I'm planning on
doing one here, soon, with the plan (at least right now) being to use the
data structure of Land's symbol manager with a stand-alone interface so it
can be used with Map, as well, not forcing the user to have Land running.

[gizmowiebe]

I like the folder Idea. I can create a Listbox witch will show different folders for each group. And than maybe a INSERT button to insert blocks innto the manager.

[j buzbee]

It always amazes me that people don't realize that a dwg file is a database
.. . . with a multitiude of wonderful tools to access and manipulate it.
Have you thought about saving all your blocks in one drawing, residing on a
server, and then accessing the blocks via ObjectDBX? Grouping could be
easily handled by naming: A_BNAME_001, B_BNAME_002, etc. Modifiying,
updating and managing this "database" could be handle with tools you already
understand: AutoCAD.

just a thought.

jb

[TomD]

"j buzbee" <jdb@journeysendfarm.net> wrote in message
news:41d45f77$1_2@newsprd01...

It always amazes me that people don't realize that a dwg file is a
database . . . with a multitiude of wonderful tools to access and
manipulate it. Have you thought about saving all your blocks in one
drawing, residing on a server, and then accessing the blocks via
ObjectDBX? Grouping could be easily handled by naming: A_BNAME_001,
B_BNAME_002, etc. Modifiying, updating and managing this "database" could
be handle with tools you already understand: AutoCAD.

I wouldn't prefer it, but I also wouldn't have a problem with what you
suggest.

[Jorge Jimenez]

Need to keep in mind that the dwg database
is not multiuser.
So if you plan on having more that one user
updating and managing this dwg "database"
then using the dwg is not a good idea.
--
Saludos, Ing. Jorge Jimenez, SICAD S.A., Costa Rica


"TomD" <tdivittis.no@spam.cecinc.com> wrote in message
news:41d94b2e$1_1@newsprd01...

"j buzbee" <jdb@journeysendfarm.net> wrote in message
news:41d45f77$1_2@newsprd01...
It always amazes me that people don't realize that a dwg file is a
database . . . with a multitiude of wonderful tools to access and
manipulate it. Have you thought about saving all your blocks in one
drawing, residing on a server, and then accessing the blocks via
ObjectDBX? Grouping could be easily handled by naming: A_BNAME_001,
B_BNAME_002, etc. Modifiying, updating and managing this "database"
could be handle with tools you already understand: AutoCAD.

I wouldn't prefer it, but I also wouldn't have a problem with what you
suggest.

[j buzbee]

True, however in most AE firms, or anywhere that office "standards" are
kept, the task of managing data falls on one (or a few) individual(s).

I have two drawings: AECStandards.dwg that users access and
AECStandards-edit.dwg. The latter being a mirror used for management
purposes. When it comes to AutoCAD objects, i.e. Layers, Blocks,
Textstyles, Dimstyles, AEC Styles, etc. you can't beat the resident modifing
tools. IMHO.

jb