Results 1 to 3 of 3
  1. #1
    pfraziervb is offline Novice
    Windows 10 Office 365
    Join Date
    Jul 2022
    Posts
    1

    Access 365/SQL 2008 Trigger Problem

    Hello.
    I have an Access application that runs fine on 2007 but not 365.
    Tables are DSN-Less linked from a SQL 2008 server.

    Everything works except for a routine that processes payments.
    It works like this:
    The access program writes a record to a table (dbo_Payments)
    Once the record is written, it sets the value of a bit field (PayNow) to True
    There is a SQL trigger that fires when the value in the field is changed
    The trigger calls an SP which processes the payment (sends to processing company via HTTP).

    The problem is when the SP runs it writes a record to a log table (PaymentLog). Under 365 I get an error in Access stating that PaymentLog couldn't be accessed.


    I'm confused because I don't get why Access would even know about what the SP is doing.
    What's different in 365 that's allowing it to see what the Trigger/SP are doing?

  2. #2
    Join Date
    Jan 2017
    Location
    Swansea,South Wales,UK
    Posts
    4,861
    That might be a 365 bug. It has been having strange problems with files in the latest version. If you are on 2206, rollback to a previous version. For a test at least.

    Read this link https://www.utteraccess.com/topics/2.../posts/2801727
    Please use # icon on toolbar when posting code snippets.
    Cross Posting: https://www.excelguru.ca/content.php?184
    Debugging Access: https://www.youtube.com/results?sear...bug+access+vba

  3. #3
    Join Date
    Jun 2010
    Location
    Belgium
    Posts
    1,035
    SQL 2008 is a very old version and even extended support has been stopped since 2019. As a fact we have reached the lifetime end of SQL 2012. I would advise to upgrade your SQL server to 2019, or at least 2016, because running a 2008 is a serious security risk.
    So, when you get an error, I would check on the SQL server if every process is still running as it should. If the trigger fails because it can't write to the log table it can lock the current record and as such give an error to the user interface application, in this case access.

Please reply to this thread with any new information or opinions.

Similar Threads

  1. Replies: 14
    Last Post: 03-27-2019, 09:08 AM
  2. Replies: 1
    Last Post: 02-23-2015, 07:06 AM
  3. Replies: 8
    Last Post: 12-31-2013, 01:09 PM
  4. Replies: 3
    Last Post: 04-30-2012, 04:09 AM
  5. Access 2010 through VPN and Win Server 2008
    By feguillen in forum Misc
    Replies: 1
    Last Post: 12-01-2011, 06:20 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Other Forums: Microsoft Office Forums