Linking a Field to a Dynamic Block Lookup

[Rico]

Okay, so I've got this block that I'm experimenting with (It's a DB that I took from the sharing thread) and I want to be able to modify the FIELDS held within to reference the distance set via lookup but to spit out the value in text based form.

in other words, when a new lookup is selected in modelspace (i.e.: VCT, CPT, CONC), the block returns the VCT, CPT and CONC values. Each lookup references the corresponding distance parameters found within and when the lookup is enabled, the lookup stretches the line to the required distance.

I was able to do this in the first block (good one), but, despite the fact that I have duplicated this method within the second block (bad one), I have been unable to get a text based result to my field request. at best, i get a numerical value.

I am sure it's something I am overlooking something, but you know when you stare at something too long and need a second set of eyes to look? Yeah, this is one of those times.

So please. If you are a field pro, have a look and let me know where I am screwing up.

[Chris.N]

Okay, so I've got this block that I'm experimenting with (It's a DB that I took from the sharing thread) and I want to be able to modify the FIELDS held within to reference the distance set via lookup but to spit out the value in text based form.

in other words, when a new lookup is selected in modelspace (i.e.: VCT, CPT, CONC), the block returns the VCT, CPT and CONC values. Each lookup references the corresponding distance parameters found within and when the lookup is enabled, the lookup stretches the line to the required distance.

I was able to do this in the first block (good one), but, despite the fact that I have duplicated this method within the second block (bad one), I have been unable to get a text based result to my field request. at best, i get a numerical value.

I am sure it's something I am overlooking something, but you know when you stare at something too long and need a second set of eyes to look? Yeah, this is one of those times.

So please. If you are a field pro, have a look and let me know where I am screwing up.did you start with fresh attributes, or copies? that one took a while to figure out, and i must have forgotten how, cuz i'm stumped with yours agian.... :screwy:

[Rico]

did you start with fresh attributes, or copies? that one took a while to figure out, and i must have forgotten how, cuz i'm stumped with yours agian.... :screwy:
well, it was one of the blocks posted in the sharing thread. I can't remember which one, and i'm too lazy to go look :razz:

But I started with the originals and switched to new ones. I made a backup of each one before I changed them and kind of worked in conjunction with both of them.

what's weird is that it works on the ones shown in modelspace, but if you insert a new copy ..... it changes to numerical values ..... even the good one .... i can't figure it out ..........

i wanna use a field to reference the distance and extrapolate the value instead of using vis states or links to other plans and all that other ****. a simple block .............. but really complex .....