| Re: Using dropdown [message #849 is a reply to message #848] |
Fri, 25 May 2007 12:56   |
AJM
Messages: 2350
Registered: April 2006
Location: Surrey, UK
|
Senior Member |
|
|
You seem to be describing two problems here:
1 - you cannot navigate from the LIST1 form to the MULT1 form without getting the 'Primary key (unique_sequence) is not complete - check selection' error.
2 - the dropdown will not save changes on submit.
Problem #1 should be easy to solve. The MULTI1 form will not work unless it is passed a selection string in the format "unique_sequence='whatever'", in other words a string that provides a primary key of the table in question. Do the records in your LIST1 form have a primary key named 'unique_sequence'? Is that field included in the select list of the sql query?
Problem #2 is confusing. I have several MULTI1 forms with dropdown lists running in my development environment without any problems.
You say that you changed "require 'std.multi1.inc';" to "require 'std.list1.inc';" and it listed the records without error. Are you aware that a LIST1 form will work without selection criteria while a MULTI1 will not? You have to select one or more records in the parent form before activating the MULTI1 form with a navigation button. Also, a LIST1 form is read-only and will not allow any field to be changed. If you are running the LIST1 control script with the MULTI1 XSL stylesheet then the screen may appear to accept changes, but when you press SUBMIT there is no code inside the LIST1 script which will update the database. You cannot run controller scripts with the wrong XSL stylesheets.
Tony Marston
http://www.tonymarston.net
http://www.radicore.org
|
|
|
|
Radicore Forum
Search
Help
Members
Register
Login
Home
