Search results

  1. L

    Return field name into array where field is true

    Yes that would make more sense. I couldn't see the forest for the trees.
  2. L

    Return field name into array where field is true

    Ok it is all working as expected with the new database structure - I now have a single table with just the DocID and the associated issue that goes with. I have created a form with full descriptions and this adds and removes records from this table appropriately. In the spirit of optimising...
  3. L

    Return field name into array where field is true

    I did have to ask - I am guessing I should be using rs.close set rs = nothing whenever I open a recordset (such as in the Form_current above)?
  4. L

    Return field name into array where field is true

    Thanks again MajP I was going through your database example again today and liked the way it used a "virtual table" and mirrored the form to the table. My only concern with this was that when I did have to make changes (which are infrequent as you have guessed), I have to make changes to the...
  5. L

    Return field name into array where field is true

    This was for the original problem where the database had been set up so that the table had all the issues listed for each document as Y/N columns. This array could be used to convert a list of individual document issues to a textbox, email or document that has the description of those issues...
  6. L

    Return field name into array where field is true

    Just for completeness here is the code I used to get the name of the "true" fields. I set the array to be the maximum number of fields, then include only the true field names and redim it to that number. This was just hacked together late on a Friday and I need to clean it up especially around...
  7. L

    Return field name into array where field is true

    The_Doc_Man: not afraid of VBA, I was just basing my concerns on the idea that I would not be able to use continuous docs (to display 'virtual' records) and instead would have to use a flat form with each check box requiring an event (that is a lot of mucking around). I was also concerned about...
  8. L

    A better way to design tables and forms?

    I will check out the database but virtual records, if it is what I think it is, sounds promising.
  9. L

    Return field name into array where field is true

    Picture for review with post above:
  10. L

    A better way to design tables and forms?

    I am sorry this is cross posting but these original posts did ask separate questions and it was suggested I start a new thread when they diverged. Here is the form explanation from the other thread: ----- Problems 1-6 are generic problems for a form (eg not legible). Then the specifics for...
  11. L

    Return field name into array where field is true

    For a bit more information I will attach a picture of one of the forms that is currently in use for a document. Problems 1-6 are generic problems for a form (eg not legible). Then the specifics for this form begins. "7 The name of the principal is missing in the document" This is on page 1 -...
  12. L

    Return field name into array where field is true

    As you know from the other thread there was not an answer to the question of how to achieve the form input with the correct schema. The closest answer was to hack together some VBA. https://access-programmers.co.uk/forums/showthread.php?p=1661631 I had the new design but no way of translating...
  13. L

    Return field name into array where field is true

    OK after creating new thread it looks like the better DB design would require a lot of custom VBA programming to display the forms (and possibly some resource intensive lookups etc). I will further investigate the change of DB design as a separate project but in the short term I will have to go...
  14. L

    A better way to design tables and forms?

    I am inexperienced, but smart enough to seek guidance from those with more experience. By your very own words 'hacking together functionality with VBA' does not seem like the most efficient way to go with the forms and display. My point is that the correct DB structure actually makes the forms...
  15. L

    A better way to design tables and forms?

    On average it is about 15-30 possible problems per document. The users don't have to select yes or no for everything, they just work through the list and tick the problems they note. This is definitely the way they want to do data entry. With the issues ordered by page number it is quick...
  16. L

    A better way to design tables and forms?

    Thanks Pat. I will take on board all the field/naming conventions and include them in the final. It is always good to improve the basics. Unfortunately the drop down form list would not suit the current work flow. The users use the subform as a checklist/'cheat sheet' for the issues they...
  17. L

    A better way to design tables and forms?

    Yes this is the behaviour I am trying to correct. And is described above as the old design but looking to change with the new design. This link is only to the "IssueAppliesTo" field - in other words each problem only applies to one particular document type and this is stored for ease of...
  18. L

    A better way to design tables and forms?

    the original question probably still stands - how do I make a form, with check boxes to fit into the above structure?
  19. L

    A better way to design tables and forms?

    OK I will update. I'm not sure if I understand this - when you say that all of the fields in tblIssuesMatrix should be their own fields in tblDocumentIssues isn't this just the current set up I have which seems inefficient? If there are 100 possible problems doesn't that mean there is at...
  20. L

    A better way to design tables and forms?

    Thanks for this - I have tried adding the tblDocumentTypes twice in the relationship view (it automatically creates tbDocumentTypes_1) and unlinked/relinked. But when I close and open the database it automatically recreates the original link and orphans tblDocumentTypes_1. Is this what you...
Top Bottom