Hi guys,

I'm creating a split form for users to:
1) Find a supplier they are looking for (In the Form section of the split form, data from tblSupplierNaming)
2) Select the supplier found by the database and displayed in a listbox (upon selection, records for that supplier will be displayed in the Datasheet section, data from tblTierPricing linked to tblSupplierNaming via SupplierID)
3) Edit or insert new pricing (In the datasheet section, data from tblTierPricing )

To do this, I inserted the required fields (to display in the datasheet section), but I set them to be not visible, so the search controls will only be displayed in the Form section.
Similarly, I hide the columns in the Datasheet section 'representing' the search fields, so only the required fields are shown.

However the weird thing is when I view the form in Display view, everything seems to be locked up. I can't select any of the search controls in the Form section or enter text to start the searching. But when I click on any of the fields in the Datasheet section, the search controls will then be enabled. All search controls in the Form section are enabled and not locked.

I need the search controls in the Form section to be active once the form is brought into view.

Can anyone enlighten me on how to deal with this?
Attached is a screenshot of the split form I am creating.

Can you zip and post your DB in 2003 format?

Kevin

Hi Kevin,

as attached.

Thanks in advance!

A couple of things: (In my opinion..)
1. Your relationship structure may be causing a problem. You might want to post a new thread and have someone double check to make sure everything is structured correctly.
2. You did not need the Inner Join for your Recordsource, simply the tblTierPricing Where SupplierID = intSupplierID is sufficient
3. You did not have any code to turn your controls On after a Supplier was selected
4 Your Form was setup as DataEntry, which is for New Records only, it does not allow viewing or editting of existing records.

Now you may have these settings above for a reason, however my opinion is they are either unnecessary (ex. #2) or problematic (#4).

I was unable to duplicate your issue both before the changes above and after.
I attached the db with the above settings.
See if the attached db or any of the settings above in your db solve your problem, if not, maybe someone else will have an idea.

Good luck,

Kevin