Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    singulars
    1. This table or related slice is empty.
    1. POHow to make the following code simpler with Arrays
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USDavid-W-Fenton
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COcheers for the comment. I do make sure that all required fields are filled in and prompt a user to do so or they cant save a record, or they can cancel. The issue here relates to emptying disabled fields that could have, in the process of a user filling out fields and changing their details, information in them. On save record i empty out all these value, but i need to prompt the user 'just in case' they may lose info that they may not to. May sound a little convoluted but in the context of the form and data it is appropriate, i think!
      singulars
      1. PO
      1. USnoelmcg
    2. COI think you're mis-using Access if you're doing all this in an unbound form, which it sounds like you are. Unbound forms are harder than bound forms -- everything about Access is designed for using unbound forms. You get a whole bunch more form-level events when you use a bound form and those can give you a lot more control over the process than when you have an unbound form. So, in short, I see no good solution to your problems if you choose to go the nonstandard route of using Access in a way that contradicts its fundamental design.
      singulars
      1. PO
      1. USDavid-W-Fenton
    3. COits not an unbound form. Im using the checkboxes so that the user has to sequentially fill in sections. E.G Invoice sent -> Fee paid -> Fee Lodged. If the details aren't filled in from the previous section then the user cant move on to the next. Problems can arise if the user goes back to edit items, and may disable fields with data in them.
      singulars
      1. PO
      1. USnoelmcg
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload