Search results

  1. L

    Link scrolling of 2 Web Browser Controls

    Thanks for the sample. I think to actually get to the scroll bars within the control is difficult and needs to be sorted before I possibly implement the above. I found some good discussion in this thread: https://www.access-programmers.co.uk/forums/showthread.php?t=307425
  2. L

    Link scrolling of 2 Web Browser Controls

    I have 2 Web Browser controls on the one form (webLeft and webRight) which both have a .pdf loaded. I am hoping to link the scrolling between them so that if I mouse or keyboard scroll in one the other scrolls by the same amount. Is this even possible in Access for Office 365? There appears...
  3. L

    Drag & Drop Outlook .msg to Form

    I did not find a way around it but had to get our IT to update the permissions in Outlook. As you have found it is related to Outlook's 'Trust Center" settings --> Programmatic access. For some reason our organisation left this option blank (which is effectively "off") when they moved from...
  4. L

    Dcount since last sunday

    Thank you both for your help - a combination worked. It errored out with vbMonday so had to use "1", also it did not like Format in the weekly expression: DCount("*","[tblDocumentLog]","Int([DateCreated])>= #" & (Date()-Weekday(Date(),1)+1) & "#")Opposite to this, the monthly would only work...
  5. L

    Dcount since last sunday

    I am trying to get a running total of documents we process during the week, displayed in an unbound text box with a dcount as the value. I have managed to get the daily count using: =DCount("*","[tblDocumentLog]","Int([DateCreated])= #" & Date() & "#") But I am struggling with the correct...
  6. L

    Mixed fields design suggestions

    Sorry this was autocorrect on the phone - the fields are named without spaces (didn't autocorrect them in the 4th paragraph for some reason) No the [DoctorName] is only used for the "GP" facility type which is a 'write-in' field. It is not used for any of the first 3 fixed-list facility types...
  7. L

    Mixed fields design suggestions

    I am trying to figure out the best way to design a table and form to achieve a result. I have 3 fields which I need users to enter: [Facility type] - one of 5 options: hospital, racf, community service, GP and Other. I have a set list for the first 3 options which I want to restrict users to...
  8. L

    Lookups - the finer points

    OK - I hadn't considered the data view post making someone inactive. I have added the suggested msgbox warning and I have sorted first by inactive. I have also added a spacer "--" and everything below and including the spacer is inactive. This separates up the list quite nicely.
  9. L

    Lookups - the finer points

    I didn't find this to be the case - if I set a the Where criteria to be True for active in the cbo query it only renders with those rows, it does not show blanks.
  10. L

    Lookups - the finer points

    I could filter the active through the query - thanks for the great idea. When I looked in the query at the back end I did notice that Access autocreates a hidden copy of the field which you select to sort and for some reason doesn't just use the sort of the existing non-hidden field. Example...
  11. L

    Lookups - the finer points

    From the first post - I do have a "Name" field to identify the person's full name. I just omitted this from my follow up comment to keep it simple. The Active flag is a great idea - I'm going to use that in another part of the database. What about the case of when there is a large turnover...
  12. L

    Lookups - the finer points

    Some jobs are done on paper in the field then entered by admin at the end of the day/week. Some jobs are done over the phone in the office and directly entered. The person doing the job is what needs to be recorded and it is not always the person entering the data.
  13. L

    Lookups - the finer points

    I probably didn't explain it correctly - its not a database action that I am tracking but the actual work order. It's the initials of the person completing the job, not entering or touching the database.
  14. L

    Lookups - the finer points

    Thanks for all the replies. I am aware of the evils of table level lookups and this is my reason for the questions. The advantage of table lookups for novices is a nice wizard which sets everything up, including relationships. They pay for it later with queries etc - and I want to try to...
  15. L

    Lookups - the finer points

    I am trying to piece together the best practice for lookups and have read the basics but have some questions on the finer points of setting it up. I have seen many times: http://access.mvps.org/access/lookupfields.htm and I am trying to avoid table-level lookups. I have table with a list of...
  16. L

    Propagate entries into table based on subform field number

    I did use a loop in the end through a recordset - this is how I achieved it: Dim rs As DAO.Recordset Dim i As Integer Dim SQLStr As String DoCmd.SetWarnings False DoCmd.RunSQL "DELETE * FROM tblMailMerge;" DoCmd.SetWarnings True Set rs = CurrentDb.OpenRecordset("SELECT * FROM...
  17. L

    Propagate entries into table based on subform field number

    And Pat - I am sorry but I don't understand your explanation and how I can apply that to the problem - that is my shortcoming not yours.
  18. L

    Propagate entries into table based on subform field number

    Unfortunately the logic from @arnelgp does not work - if a user accidentally selects 2 copies and then increases it to 3 then it creates 5 entries. Also if they change the name of the medication it will not delete the old record as it cannot match the medication name. I think it would be best...
  19. L

    Propagate entries into table based on subform field number

    This is the correct idea - thanks @arnelgp. It doesn't quite fit into the workflow above but I may be able to change it to suit. I will have to move the clearing of the data from the temp table to the form load probably and include a clear all button as before the routine only ran on a button...
  20. L

    Propagate entries into table based on subform field number

    I'm trying to duplicate data to print multiple labels. the mail merge side is all set up - it points to the tblMailMerge and works fine. I just need to duplicate the entries in the Mail Merge table so that Word makes multiple pages which get fed through to the printer. The old way was: Table...
Back
Top Bottom