Originally Posted by
LostInAccess
...If I select a Record Source for the Form, it then limits me to the number of records in that source (table or query) and the different text boxes i have populated (via an event of the combo boxes) maintain the original field selections as i scroll through the records (don't change per record).
If the Comboboxes are Bound to a Field in your Form's underlying Table or Query, they will change and be Record-appropriate as you move from Record to Record.
You shouldn't confuse the RowSource, i.e. the Table or Query the Combobox is based on, and the underlying Table/Query that your Form is based on and to which the Combobox can be Bound.
To be honest, I have no idea what you mean by "...If I select a Record Source for the Form, it then limits me to the number of records in that source (table or query)..."
Access is designed to be used with Bound Forms. By doing this, the Access Gnomes automatically take care of most of the heavy lifting involved in saving Records! A big part of the reason to use Access for database development is the speed with which it can be created, using Bound Forms. Several developers I know, experienced in Visual Basic database development and Access development, estimate that development, using Unbound Forms, by highly experienced developers, takes twice as long as it does when using Access and Bound Forms.
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 if far, far better than anything you can do in Access
So my question to you is is why are you going about this the hard way?
Linq ;0)>
The problem with making anything foolproof...is that fools are so darn ingenious!
All posts/responses based on Access 2003/2007