Blank form

[Tom Stoddard]

I'm cross posting this question because it seems to be related to the
combination of form design and security.

I have a split database which I recently implemented security on.

I set up security on the BE tables of my database so that some users have
read only and others have full permissions (read, update, delete & insert)
to the tables. I created a simple form based on a query on 1 table and put
bound controls on the form to display all fields from the query. Both users
could use the form.

I then added a combobox based on a simple query on one other table. I tested
the form and both users could still use it.

I then put a reference to the combobox in the criteria field of the query
grid of the query that the form is bound to and put this code "Me.Requery"
in the combobox onAfterUpdate event. When the user with full permissions
uses the form the user can change the selection in the combobox and the form
requeries and filters the records it displays. When the user with read only
permission on the tables tries to open the form its blank. Non of the
controls are visible.

I even tried using the Form's Filter property instead by putting "CustomerID
= [Forms]![frmTest]![cboCustomer]" in the filter property and setting
Me.FilterOn = True in the form's load event. I got the same result. It
worked for the user with read/write access but not for the user with read
only access.

Can anyone explain this to me?

 

[Chris Mills]

I'm not quite sure if this is the problem, but if you use the Form Header
rather than the Detail section of the form to place the combobox (and anything
else you want permanently displayed like buttons), they will remain displayed
even when there are no records.

It may be that in one case "New Record" is displayed when there are no other
records, and in the other case (read-only) there are no records at all
selected by default.

Chris