I create a field with a valuelist. I make it a pop-up, so that users can choose a value. I publish this highly sophisticated db through the webcompanion. So far, all works OK.

Then I change field format - popup: I allow the user to edit valuelists. That works ok when I change data in FMP6 itself, of course, but in the browser I never get to see 'edit'.

Is that a failure on my side to change something regarding userrights/sharing/what have you, or does webpublishing simply not allow for this feature?

IMHO -- it does not working on web.

IWP - intuitive web publishing

Tune in to your computer's electrons.

This message brought to you by the Psychic Procrastinators.

Okidoki, no editable valuelists in (intuitively) published dbs.

*adds entry to 'FM oddities' book*

There isn't middleware program, which will do that so I do not support entry in the 'FM oddities' book Is just how the web works and it has nothing to do with FM.

But is piece of cake to do it through value list generated from records in another file I do use that often.

Ooh, that sounds interesting! Mind explaining a little further about value list generated from records in another file?

Thanks

That is standard FM function, best is to press F1 and see the Help.

Look into "value lists" and "Defining a list of values for data entry".

BTW Related Values also cannot work on web as they are working in FM, but that can be achieved with JavaScript.

Hi, like so much of publishing FMP through a browser interface you gotta think differently!

To expand on the "other file":

make little separate one-field databases and define your value lists from that. Just add or delete records to edit the value list.

(you might even find that database useful for displaying portals as well)

If you want a user to add values not in the list into a form, just include an "other" box under your popup and use a calculation field like:

theFieldValue=

If(isEmpty(other),thePopupField,other)

regards, jeff

Thanks for the explanation

I tried to include editing valuelists by editing another db in a script, but you guessed it: works fine until I IWP it