mysql - Access: How to structure input vs read only forms -


ive got peoples db , after development recordset main form not updatable because of subqueries etc etc..

all because redesigned db resemble real life more, meaning added tables track things. made relations little more complex , im left db cant add new records or edit hahaha , thats pretty useless

so i'm left thinking can't me there either simple solution can't see or have designed forms totally wrong.

whats praxis in design/structure when have/get form based on recordset that's not updatable in "regular" peoples db , want add or edit details in it? (think hr managment db)

relationships

(reason recordset being un-updatable: recordset based on query gets records 3 related tables , max function on date field recent record on 2 of tables)

now have mainform , 3 subforms on it. can edit/add info in subforms of course mainform displaying names , other personal details not updatable...

the mainforms query querying tblperson, tblinmate, tblclassificationhistory , tblsquadhistory...

in case, recommend 2 possibilities:

  1. build form input , edit data persons record source tblperson. input/edit-form can open in main form via button or ribbon example. can build 1 form input , edit data , change behaviour vba-code (or macros?). or can build 2 forms edit , input data seperately. can add ok , cancel buttons safe or undo changes. possibilities endless. basis access knowledge , there tons of tutorials out there, not explain further.
  2. change query on main form. if have continuous form , not want add new form, should edit query. can not estimate described query complexity given information, there must way "max-date"-recordsset without aggregated ("group by" -statement) query results. goal change main-form query, not have "group by" part. aware can use subquerys "group by" finding "max-value". should check main form query, if need queried fields main form. let 3 subforms data query work.

basically, perfect user interface (ui) forms in access depends on users preferences, expectations , use case itself. have find out, design suits best application. can research on ui design patterns if want knowledge recent experiences. huge field of expertise!


Comments

Popular posts from this blog

java - Date formats difference between yyyy-MM-dd'T'HH:mm:ss and yyyy-MM-dd'T'HH:mm:ssXXX -

c# - Get rid of xmlns attribute when adding node to existing xml -