Recent content by JohnPapa

  1. J

    Calculated field in query

    Yes it is a small island in the mediterranean, a stark contrast to Silicon Valley California where I used to live.
  2. J

    Calculated field in query

    Yes, I am very surprised as well. The culprit is the List Separator, which was set to ";". When I set it to ".", the original expression worked.
  3. J

    Calculated field in query

    It appears that the following works. Expr1: DateAdd("m";[lngMHMonth];[tblMedicalHistoryListNew].[dtmCreation]) Where in the documentation does it say to use ";" instead of "," ?
  4. J

    Calculated field in query

    It shows the dtmCreation field on mine
  5. J

    Calculated field in query

    When I run the query without the Calculated field I get what appears in the attachment.
  6. J

    Calculated field in query

    Yes the fields have values. What is CamelCase? Not clear what you mean with [&]
  7. J

    Calculated field in query

    I get the error message which appears in the attachment when I try to create a Calculated field using the DateAdd function. Any ideas?
  8. J

    Unable to create .accde

    Tested it again this morning. I tried it with Bitdefender on. It gave the problem. I disabled Bitdefender for 5 minutes and I was able to create the .accde immediately.
  9. J

    Unable to create .accde

    I mentioned it immediately after I found out. I found out though another ticket which I opened yesterday.
  10. J

    Unable to create .accde

    I found out today the reason of the problem regarding the inability to create a .accde file in A2013. This thread has 50 entries and surely a source of great information and once again I thank everyone for their contribution. The problem was caused by my antivirus, BitDefender. Once I disabled...
  11. J

    Cannot create .accde in 64-bit

    Fixed. I was able to create the 64-bit .accde when I disabled the antivirus software, in this case BitDefender. With the antivirus on on different pcs, the 32-bit .accde is created , while the 64-bit is not. So if you are having problem with creating .accde, you may look at any antivirus...
  12. J

    Cannot create .accde in 64-bit

    Wanted to add that the .accdb appears to run ok
  13. J

    Cannot create .accde in 64-bit

    I get, "Could not use <Specific filename.accdb>. File already in use." when I try to create the .accde using 64-bit A365. The .accde is created ok when I use the 32-bit A365. Both the 32-bit and the 64-bit use the following Version and Build
  14. J

    Interface between Access 365 with Calendar in 365 Business

    The following works fine and deletes ALL the filtered appointments. Many thanks. I will post both the Delete and Export Code again. Dim i As Integer For i = olFilterAppointments.Count To 1 Step -1 olFilterAppointments(i).Delete Next
  15. J

    Interface between Access 365 with Calendar in 365 Business

    The number of filtered (to be deleted) appointments is olFilterAppointments.Count When you say Loop do you mean using For Each ...Next. I will remind that we are talking about a Collection with no apparent unique ID and the current Delete loop is For Each olAppointmentItem In...
Back
Top Bottom