Searching for Excel

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • jimatqsi
    Moderator Top Contributor
    • Oct 2006
    • 1293

    Searching for Excel

    I'm writing an application for a client that is clinging tightly to the old days. They still run XP and Office 2003 on most of their machines. I'm developing in a Win 7/Office 2007 environment.

    One of their programs is written to import data from Excel. There is no reference to Excel until / unless you run that program.

    They have a test machine for me. It has Access Runtime installed, along with Office 2003. When they launch my program (front-end .accde linked to several .mdb files) they get a message "Searching for Excel." It appears for around 10 seconds and then disappears.

    When they launch my program using the .accdb version of the same database, they get an error message. They can click through it and continue. Various odd errors pop up when we're testing (we don't test the import anymore, it works okay). Also, one error I've seen perplexes me
    -Error 3075, line 0 function is unavailable in expression in query expression Format(Lastcall date,"mm/dd/yy")

    Is that saying Format function is unavailable?

    All this stuff works well for me in my testing on both runtime and full Access. Any ideas about why we see the various messages and errors?

    Thanks,
    Jim
  • twinnyfo
    Recognized Expert Moderator Specialist
    • Nov 2011
    • 3662

    #2
    Jim,

    So, your project does not call for Excel, but when they open your project in Access RT, you get the Excel Message?

    And for the Error 3075, is there any possible way you could be able to pinpoint where in the code this error is being generated? I can only assume that you use the Format() Function in multiple places in the code?

    I've seen strange things happen after a compile, but not quite that strange....

    Comment

    • jforbes
      Recognized Expert Top Contributor
      • Aug 2014
      • 1107

      #3
      This may be what you are getting into, or at least similar since you are crossing versions of Access: http://support.microsoft.com/kb/194374

      You also might be running into some late binding issues. With late binding, which you can do to Excel, you get around some versioning with Office. The downs side is that there is no reference the library so the compiler can't check for errors and possibly in this case the count of arguments may be off.

      ... Just some thoughts.

      Comment

      • jimatqsi
        Moderator Top Contributor
        • Oct 2006
        • 1293

        #4
        Yes, I get this "searching for..." message, but only from the .accde version, not the .accdb version. I have very little experience with .mde/.accde files. Those files make it impossible to break into the code when an error message pops up. I'll add some logging within the program if I have to.

        Thanks for that link, jf, that may be very helpful. And I may have to change to late binding.

        Thanks,

        Jim

        Comment

        Working...