The filemaker server document in the "documents" folder actually has really good advice about which technology to choose.
Look for the CWP document
I've been attempting to do this via webdirect and it has been working, but I've run accross some issues with web direct, especially if the browswer window gets refreshed and the record being viewed changes to another persons record when the web page refreshes.
that’s weird. There must be something else going on.
Also in the URL address it shows in web direct record=10 in the URL address. if you change the 10 to say 20 and hit return, it refreshes the page to the databases record #20.
That’s normal. WebDirect and IWP before it are both susceptible to this sort of URL manipulation. You must secure the data using User Accounts and Privilege Sets.
Jeremy, just to clarify:
You can custom web publish using different grammars of XML. You may use PHP or other web applications that can process the XML. FMS happens to have an API in PHP that uses one of the grammars of XML.
You may also use ODBC/JDBC to publish data to the web using a web application that can make the queries and process the result.
Think of this like creating layouts and then using scripts to do something with the layouts. This is very broad, but the comparison is the ratio of time spent on creating a good looking layout and the scripts for it. Web sites are somewhat are like that.
The Web direct does the work of re-creating your layout(s), but as you've found may not have quite all the features you desire. If you wish to pursue the custom web publishing, then your options are:
Hire someone to do it for you.
-- sent from my iPhone4 --
You might consider redesigning your solution such that you have a table with only one record in it and all global fields that get loaded with data as needed. Then when the user is ready to "submit" their record, you write it back to the proper tables in a script.
This is pretty much how I handled a IWP I wrote years ago, and it worked well because of the limited requirements.