Completely stumped - help please?

[LDK]

I've got a form based on a set, and want to save a value to a field on the child table, using the CanSave event.
As it is currently set up, I get an "Invalid Argument passed to A_RULE API." However, the data is correctly changed in the child table.

If I restrict the form to disallow edits, or if I make the field read-only, the error is "Field types don't match"

I think I'm missing something basic, but I can't for the life of me determine what it is. I'm uploading a simple database that shows the error. The form is INPUT, and I only input the first 2 fields before saving. The problem field is "TF".

test db.zip

[Tom Cone Jr]

Re: Completely stumped - help please?

1) Your canSave event script attempts to begin a new child table record before the parent table record has been commited. This is a no no. The parent table record must be commited so Alpha can assign the link field value to the new child table record.

2) Your CanSave event script attempts to change field values in the parent record as it's being saved. This is a no no. Sets up circular logic that can never end.

3) Your form includes the child table link field. Since your form is based on a set, Alpha will supply the link field value for you. It's a mistake to include that field on your form.

4) In one to one sets the form level events fire for both parent and child tables. This leads to circular logic, also. When you try to save the new child table record the CanSave event fires, which assigns field values to the record being saved. A no no.

You'll find life with Alpha to be much simpler if you design your forms so that the user works with a single table at a time. Do not permit the user to begin the related records until the parent has been committed.

May I ask what your background database experience might be? You're pretty far off the beaten path here, so I'm curious whether you're being influenced by systems where forms are not so tightly bound to their underlying tables.

-- tom

[Ted Giles]

Re: Completely stumped - help please?

LDK.
Take heed of Tom's wise comments, and I suggest you try the following as well. (Easier than using Xbasic)
In the fields you want to set on Save, put a Default value in the Field Rules
Click on the Set and save the Form as something else to work with later. The Set based form is how Alpha will link all of the bits together for you.
See attachment.

[jacobr]

Re: Completely stumped - help please?

Is there a way I can change the table/set bound to a form or add a table to add more fields?

[Ted Giles]

Re: Completely stumped - help please?

Renny, not sure what you mean but;
I believe that Forms are bound to Tables/Sets.
You can delete a Form, but if you delete a Table/Set, the forms go as well.
If you restructure a Table and add fields, as long as the Linking field used by a Set isn't changed, the set should still work.
Any Forms you have attached to the Table or Set will NOT automatically have the new fileds shown. You need to add them manually.

[Tom Cone Jr]

Re: Completely stumped - help please?

Renny, in addition to Ted's good advice you can "copy" your form to another table ( or set ). However, if the second table has a different structure some or all of the objects in your layout will be "broken" until you bind (associate) them to the fields in your second table. This is done by opening the form in design mode, then right clicking on all the broken objects and telling Alpha which table field you want to display through each object.