A more robust query mechanism for worksheet databases

[Petri]

If an innocent user changes the name of a layer or a class, a query may be ruined. When an average user sees a message saying something like "the criteria are invalid and you have to change them in VectorScript" he or she will simply panic.

No normal human being can deal with an error in something like

=DATABASE(((L='SURFACE MATERIALS') & ((T=ARC) | (T=POLY) | (T=POLYLINE) | (T=RECT)) & (C<>'MATERIAL-Asphalt') & (C<>'MATERIAL-Concrete') & (C<>'MATERIAL-Stone')))

I'm not sure how this could be resolved. In FileMaker Pro, all names of tables, fields, layouts, scripts etc. a user (or even a developer) sees are "aliases"; internally they are, I gather, persistent numbers.

VW classes are numbered, but the numbers are not persistent - and probably could not be: classes can be added by copying and pasting objects or by any other simple action.

Maybe we could have aliases (alternative layer & class names) that would be used in the normal user interface, including queries & reporting, in the same fashion as we have alternative parameter names in PIOs?

PIO reports, by the way, should be able to use those alternative names. Localisation of objects is rather pointless if users need to figure out what the "real" name of a parameter is.

In this respect, alternative names for data record fields would also be welcome.

[boxjoint]

Localisation of objects is rather pointless if users need to figure out what the "real" name of a parameter is.

Speaking of which, why is there no easy way for users to see a list of these names and their alternates? I know we can use the Plug In Editor but this is neither user friendly nor convenient.

I recall a post about this topic some time ago where Robert Anderson suggested to the questioner that they should write a script that will return all those names. While I'm sure this is a simple task in the VectorScript 101 guide, it shouldn't be required for a user who is simply trying to set up a worksheet and needs the "real" name of a parameter.

It would have been much more helpful if Mr. Anderson had provided the script in his reply, but even more helpful would be to have it built into the program so those of us who have not yet learned Vectorscript but can manipulate a spreadsheet are not stymied.

Perhaps something like "Show Parameter List" in the menu right below the Plug in Editor?

I'd suggest that little stumbling blocks like this are a disincentive to people who might otherwise be perfectly capable of taking advantage of the power of worksheets.

[islandmon]

PIO reports, by the way, should be able to use those alternative names. Localisation of objects is rather pointless if users need to figure out what the "real" name of a parameter is.

In this respect, alternative names for data record fields would also be welcome.

Righto .. Petrisan .. righto ... off to Indja we may go .. off to Indja I know ..

speaking of FilemakerPro ... having written numerous successful databases with it ...

the GUI is really very excellent ... FilemakerPro is hands down one of the very best apps ever created ... in all the years I have used it ... NEVER... once has it failed or crashed !

[Pat Stanford]

It would have been much more helpful if Mr. Anderson had provided the script in his reply, but even more helpful would be to have it built into the program so those of us who have not yet learned Vectorscript but can manipulate a spreadsheet are not stymied.

Perhaps something like "Show Parameter List" in the menu right below the Plug in Editor?

How about this for a worksheet solution

Create a database row with a criteria of All Objects.

Put the formula =N into a databse header row cell.

Drag the SUM icon (and one of the sort icons if desired) into the column with the =N Formula.

You will have a worksheet that will show the name of every object in the file with an additional row that sums all of the objects without names.

Or am I misunderstanding you? Are you looking for a way to get all of the parameter names and alternate names for every PIO?

Pat

[Petri]

It would have been much more helpful if Mr. Anderson had provided the script in his reply, but even more helpful would be to have it built into the program so those of us who have not yet learned Vectorscript but can manipulate a spreadsheet are not stymied.

This capability does exist: when you say "Report", you get the alternative names as column headers while the real names are in the formulae.

[boxjoint]

Are you looking for a way to get all of the parameter names and alternate names for every PIO?

Pat

Pat,

Yes, that's pretty much what I was asking for.

Perhaps it's unnecessary, but I find that there are times that I don't actually know what parameter might do the job best in a formula. I'd like to be able to see the name of the PIO and it's parameter names in a list so it isn't necessary to look them up individually.

I will say that I am pretty new to this process so perhaps I am overcomplicating things.

Also, my apologies to Mr. Anderson. I searched for the post that I mentioned in an effort to get more information but was unsuccessful. My memory may be getting worse that it was before, but I can't really remember how it was before so I have no way to know.

[Petri]

I will say that I am pretty new to this process so perhaps I am overcomplicating things.

Could be. Primarily your problem is that you don't read the answers to your questions.

[boxjoint]

Primarily your problem is that you don't read the answers to your questions.

Petri,

No. You're wrong.

I read every answer carefully and appreciate the time taken by the respondents to provide them. Thank you for yours.

I did read your answer. It's helpful in certain circumstances. Specifically, when you already have an object on the drawing that you want to report on.

What I am suggesting is something along the lines of the VectorScript Function Reference which allows the user to look at all the available options in order to select the one best suited to their task.

Currently, (V12) if I wish to create an object and know that I will want to report on it later, I must do one of two things to see the parameters that are available.

1. I can open the Plug In Editor and review the objects parameters there.

2. I can place an object on the drawing and look at the object info palette, or create a report as you suggested.

If I wish to compare the available parameters of more than one object to see which will best suit my needs, the info editor is of no use because I can only see one object's parameters at a time. (And cannot print the list from there)

The same goes for the OIP.

Using your suggestion, I could place a number of objects on the drawing and create a report on each one, and then print them if I wish. (But I don't think it will print the formulas, will it?) Then, for all the objects which I will not use, I must delete the object and then find and delete the worksheet that I created for that object.

To me, that is doing things by trial and error. Why should I have to create and delete an object and a worksheet just to determine if the object will suit my needs?

I realize that I have drifted from my original suggestion which was about the availability of "real" and "alternate" names, but they go hand in hand.

Once I have selected and drawn an object, I now must determine the proper names to use in my formula so I must use one of the above methods again.

As someone who is trying to get a handle on how this all works together, I'm saying it is not very user friendly and I'd like to see a built in menu item that will provide the names of the PIO's and their parameters that I can refer to WHILE I am investigating a tool.

[Petri]

As someone who is trying to get a handle on how this all works together, I'm saying it is not very user friendly and I'd like to see a built in menu item that will provide the names of the PIO's and their parameters that I can refer to WHILE I am investigating a tool.

Well, the user-friendly Plug-in Editor does that... Sort of...

1. The Plug-in Editor not only provides the information, but also enables one to change it.

2. The Report Generator gives you column headers and formulae for each object.

The latter should be quite adequate when investigating. In order to know what a tool/object can do, you do need to place an instance in the document.

A menu item that would list the details of every tool might be interesting, but - at the end of the day - somewhat useless.