'group by' plus a specific action on form

[dn_perl]

A doubt by a complete ignoramus.

I have a table, named ttt :
fields : state, continent, capital, currency.
The user tries to input values : "France", "Europe", "Nantes",
"Dollar"

A validation routine files following errors in error_table :
"France" "Europe" "Nantes" "Check The Capital"
"France" "Europe" "Dollar" "Check The Currency"

The table 'error_table' has one more entry :
"Germany" "Europe" "Geneva" "Check the Capital"

I want to show a form which displays all fields of error_table
plus a re-submit button per row. However, if there are more than
one entry, like France-Europe has 2 entries, only one row for
France should have its re-submit button enabled, the other rows
for France should have that button disabled. The idea is that
once the user of the form sees a disabled button, he knows
he needs to correct more than one field for that record.

TIA.

[Salad]

dn*****@hotmail.com wrote:

A doubt by a complete ignoramus.

I have a table, named ttt :
fields : state, continent, capital, currency.
The user tries to input values : "France", "Europe", "Nantes",
"Dollar"

A validation routine files following errors in error_table :
"France" "Europe" "Nantes" "Check The Capital"
"France" "Europe" "Dollar" "Check The Currency"

The table 'error_table' has one more entry :
"Germany" "Europe" "Geneva" "Check the Capital"

I want to show a form which displays all fields of error_table
plus a re-submit button per row. However, if there are more than
one entry, like France-Europe has 2 entries, only one row for
France should have its re-submit button enabled, the other rows
for France should have that button disabled. The idea is that
once the user of the form sees a disabled button, he knows
he needs to correct more than one field for that record.

TIA.

I'm not sure what you need. I don't underst6and the 2 entires,
disable/enable buttons stuff since I can't see your form.

Anyway, I'd probably take another approach. I'd have a table that
would contain the country, continent, currency, capitol.

I would also create a table of continents since that is small and very
static.

Then a person could enter a country. In the afterupdate event I'd check
to see if that country existed. If so, I'd then read the record and
fill in the currency, capitol, and continent.

If it didn't exist, I'd then have a dropdown on continents, maybe a
dropdown on currency types and let a person add a currency type if it
doesn't exist.

It seems there is too much data entry work asked from the operators/users.

[dn_perl]

Salad <oi*@vinegar.com> wrote -

I'm not sure what you need. I don't underst6and the 2 entires,
disable/enable buttons stuff since I can't see your form.

Anyway, I'd probably take another approach. I'd have a table that
would contain the country, continent, currency, capitol.

I had given the example of a table about Country to make
my case clear. The real-life table I am dealing with is
far more complex.

Still let me try to show how the form should look like.

Field1 Field2 F3 F4 Field5 Button
country1 continent1 only one error for record 1 Submit
country2 continent2 three errors for record 2 GRAY-OUT
country2 continent2 three errors for record 2 GRAY-OUT
country2 continent2 three errors for record 2 Submit
country3 continent3 only one error for record 3 Submit

F3, F4 fields carry info which we can edit. So we change the capitol
of France to Paris from the earlier wrong entry in F3.

If for (countryN, continentN) there is more than one error, only
one entry for that combo should have active submit button.
Other entries for that combo should have the submit button
grayed out.

----