> I'm using FM 6.0 (on Windows 2000) and have used Claris Homepage to
> create the Web interface to the database. I'm then customizing the
[quoted text clipped - 8 lines]
> [FMP-VALULIST: Editor/Designer Name, LIST=-Editor/Designer Name]
> <checkbox symbol> [FMP-VALUELISTITEM: Always, HTML] [/FMP-VALUELIST]
This looks like fair code for what you want...
BUT
It will only work if the page it is in is called as a FileMaker format file,
eg
http://localhost/filename.html
will NOT work
http://localhost/FMPro?-db=db.fp5&-format=filename.html&-view
will
> The field (Editor/Designer Name) is derived from a value list that
> contains about 30 names. How can I get each of these names reflected
> in the Web interface AND do so in a way that allows the user to view
> a record and ADD new checkmarks to a record without overwriting the
> existing ones?
Try the above for a start.
> How can I fix this in either the Connection Assistant, FileMaker, or
> in the HTML files? (If you do have an answer for me, please dumb it
> down for a very new user. :-)
Feel free to mail me off the newsgroup - I can write some demo stuff fairly
quickly if required.
Webko
Barbara White - 28 Jun 2004 13:25 GMT
What Tim suggested below worked...the checkboxes actually appear in
the Web interface file now. (Now I just have to figure out how to
get edit permissions to "take" so that we can actually make changes
to existing records using the Web interface. I sent mail to Tim
about this.)
Thanks, everyone, for the help. Particularly, thanks to Tim for
figuring out what the problem was.
Barbara
>>I'm using FM 6.0 (on Windows 2000) and have used Claris Homepage to
>>create the Web interface to the database. I'm then customizing the
[quoted text clipped - 34 lines]
>
> Webko
Barbara White - 29 Jun 2004 14:21 GMT
I've fixed the problem with the edit permissions not "taking". I'm
not sure which of the fixes did the trick, but here's what I did.
In the FM file, if any of the fields had "prohibit modification of
value" checked, I unchecked it.
I also configured the Web Security Database to allow edit permission
for all records. (I suspect that this had little to do with the
solution because the database was set to use Filemaker access
privileges and I did not use groups or passwords on the file.)