Bound Controls?

[dccjr]

First let me say that I have no experience with bound controls. Typically, I use unbound controls (combo boxes and textboxes), then an INSERT statement to write the data to the appropriate table. In a new project I have a form with some 40-50 fields on it. This makes for a really long SQL statement. So my question are:

1. When does an bound control actually insert the contents of the control into the table?


1a. If it is upon the control's loss of focus, if the user tabs back up to a previous control, does it change what is in the table for the same record?
2. Is inserting all of the data from the form at one time the most efficient way? If not, what is a better way to do this?

I am realy concerned about exceeding the 1024 character max on a string (my SQL statement is stored as such due to concatenation). I have never worked with so many controls on one form. (It can't be split as it is a post operation checklist).

Any advice would be greatly appreciated.

[DepricatedZero]

1: The changes are applied when the record bound to the form changes
1a: It is not bound that way, however I recommend putting an "If Me.Dirty Then DoCmd.RunCommand acCmdUndo" into your navigation controls so that there are no accidental record changes
2: I'm not sure I follow. This may simply depend on your process. Could you rephrase that question please?

[Missinglinq]

Access is intended to be used with Bound Forms. Using them allows Access to do the vast majority of the heavy lifting. Data from all Bound Controls is committed to the Table when the Record is saved. The Record is saved, in turn, when

• You move to another Record
• You Close the Form
• You Close Access, itself

To be honest, if you insist on using Unbound Forms, you'd be far better off using a straight VB or C++ front end with a SQL Server or Oracle back end.

• You can create an EXE file which gives total protection to your code/design
  
• You can distribute the db to PCs without a copy of Access being on board
  
• Your data security is far, far better than anything you can do in Access

Linq ;0)>

[dccjr]

Thanks Linq. Unfortunately, I am not at liberty to use an SQL backend. Oracle is completely out of the question, as our company is a SAP user.

I think I have it fixed, but another issue has arisen. I will post in a new thread. Thanks again.