Results 1 to 8 of 8
  1. #1
    jmuirman1 is offline Advanced Beginner
    Windows 10 Access 2016
    Join Date
    Aug 2016
    Posts
    84

    An error occurred - are there diagnostic tools in access?

    Suddenly I get this error: AN ERROR OCCURRED WHEN SENDING DATA TO THE OLE SERVER (THE APPLICATION USED TO CREATE THE OBJECT)


    *You may be trying to send too much data...
    *You may be using an OLE server that doesn't accept Clipboard data...
    *You may not be able to start the OLE server because it's not properly registered...
    *Your computer may be low on memory...


    Based on recommendations by this group, I split my db several months ago. The back end is on my server and there are three users. However, I still see errors. And often upon opening Access creates a back up...which i have to use to move forward using the db...

    In conjunction with the error above, AN ERROR OCCURRED WHEN SENDING...my mail merge isn't working correctly. The pop-up "Find Recipient" doesn't work and isn't connected to the OLE server, whatever that is. To use mail merge, I have to put the table ID number in the MS Word "Go to record" field and enter the primary key [ID].

    Can you tell me how to at least begin in diagnosing the problem?

    Can you help me solve my particular mail merge problem?

    Thanks,

    John

  2. #2
    GinaWhipp's Avatar
    GinaWhipp is offline Competent Performer
    Windows 7 64bit Access 2013 32bit
    Join Date
    Jul 2011
    Location
    Ohio, USA
    Posts
    377
    Hmm, where are the Frontends?

  3. #3
    jmuirman1 is offline Advanced Beginner
    Windows 10 Access 2016
    Join Date
    Aug 2016
    Posts
    84
    the front ends are on the server and each user has a shortcut on their desktop to the fe...no good?

  4. #4
    GinaWhipp's Avatar
    GinaWhipp is offline Competent Performer
    Windows 7 64bit Access 2013 32bit
    Join Date
    Jul 2011
    Location
    Ohio, USA
    Posts
    377
    Move the Frontends to each Users machine that is where they need to be. They should each have there own. Once done see if the error still persists.

  5. #5
    jmuirman1 is offline Advanced Beginner
    Windows 10 Access 2016
    Join Date
    Aug 2016
    Posts
    84
    Thanks. How do i do that? just copy from the server and paste to the individual desktop?

  6. #6
    GinaWhipp's Avatar
    GinaWhipp is offline Competent Performer
    Windows 7 64bit Access 2013 32bit
    Join Date
    Jul 2011
    Location
    Ohio, USA
    Posts
    377
    They need to be placed in a Folder and then put a shortcut on their desktop. The Frontend folder then needs to be placed in a Trusted Location. Here's some reading...

    http://www.kallal.ca/Articles/split/index.htm

    http://allenbrowne.com/ser-01.html

    http://www.utteraccess.com/wiki/index.php/Sharing


    You may also want to take a look at MVP Tom Wickerath's article…
    http://www.accessmvp.com:80/Twickera.../multiuser.htm


    To handle the update of multiple front ends see…
    http://www.autofeupdater.com/
    http://regina-whipp.com/blog/?p=184
    http://www.btabdevelopment.com/ts/freetools

  7. #7
    Missinglinq's Avatar
    Missinglinq is offline VIP
    Windows 7 64bit Access 2007
    Join Date
    May 2012
    Location
    Richmond (Virginia, not North Yorkshire!)
    Posts
    3,016
    Gina's advice, as usual, is dead on! Having multiple users sharing a single Front End, on a network drive, is a sure way to repeated episodes of corruption, speed and timing problems, and all manner of strange, odd and curious behavior!

    Being in forced retirement, I spend 8-10 hours a day here and on other Access forums/newsgroups, and over the past twelve years have seen literally dozens and dozens of reports of split databases, using links to a single Front End, causing these kinds of problems, as well as massive data loss! The really insidious thing is that this kind of setup can work for extended periods of time before the troubles begin! But once it does, they become chronic, which is to say they occur over and over and over again! So, as Gia said, give each user their own copy of the Front End and see what happens.

    The OLE Server error usually, but not always, is associated with the opening a Form, and can be caused by all kinds of things, but to the best of my knowledge, it is very seldom, if ever, actually connected with communicating with a OLE server or ActiveX Control!

    The most common cause, going by what I've seen online for the past twelve years, has to do with using a non-English language with Access, and the need to set the language for non-unicode programs to that foreign language. Here's a link explaining this:

    You receive an error message when you start Visual Basic for Applications code in an Access database

    Linq ;0)>
    The problem with making anything foolproof...is that fools are so darn ingenious!

    All posts/responses based on Access 2003/2007

  8. #8
    jmuirman1 is offline Advanced Beginner
    Windows 10 Access 2016
    Join Date
    Aug 2016
    Posts
    84
    Thanks Linq! I deleted a chart/graph from my switchboard and that cleared up the error message.

    John

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

Similar Threads

  1. Tools to learn access VBA
    By MatthewGrace in forum Programming
    Replies: 3
    Last Post: 12-22-2016, 04:14 PM
  2. Replies: 1
    Last Post: 05-22-2013, 02:34 PM
  3. Replies: 2
    Last Post: 04-23-2013, 12:44 AM
  4. Replies: 1
    Last Post: 12-12-2012, 02:56 AM
  5. A problem occurred while Microsoft Access...
    By nchesebro in forum Programming
    Replies: 16
    Last Post: 03-04-2011, 04:19 PM

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