Why will my database work on some computers but not others?

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • Seth Schrock
    Recognized Expert Specialist
    • Dec 2010
    • 2965

    Why will my database work on some computers but not others?

    I have created an Access 2010 database and packaged it to run on Access Runtime Viewer 2010. When I install it on some computers, it works fine. On others, it doesn't work. But some of the computers that don't work and do some things but not others. So far I have gotten two different error messages. First I get a "Unknown function 'Date' in validation expression or default value on 'tblACHFiles.Da teEntered'." Then later I get another error message that says "Execution of this application has stopped due to a run-time error. The application can't continue and will be shut down." The part that stumps me is that it works on two computers. At first I thought that there was something on my computer that allowed me to make it work so I installed it on another computer and it worked. One interesting note is that the two computers that I have gotten it to work on are in a workgroup while the computers that it doesn't work on are part of the network domain. The back-end of the database is stored on a server in the domain. I checked the permissions on the folder containing the BE and it gives Read/Write/Execute/Modify permissions to everyone involved.

    I'm stumped.
  • Mihail
    Contributor
    • Apr 2011
    • 759

    #2
    I think that there are missing libraries on the computer where your database not work.
    I recently encountered the same problem with an Excel macro, after a new (but incomplete) installation for Office. I solve that by fully installation for Office environment.

    Hope this is a help for you in order to solve your problem.

    Comment

    • Seth Schrock
      Recognized Expert Specialist
      • Dec 2010
      • 2965

      #3
      Any ideas of which one? In doing research online I was thinking it might be that, but none of them say missing. I figured out that it was because of some default values that I had set to be =Date(). It does work when I change one of them to =Now(), but the other one still crashes. Also, most of the problems that I found were caused by a migration from MS Access 2003 to 2010 which I didn't do. I started from scratch using Access 2010.

      Comment

      • Seth Schrock
        Recognized Expert Specialist
        • Dec 2010
        • 2965

        #4
        Well, I fixed it but I don't know what I did. I created a brand new database and then copied and pasted everything from the old database into the new one. I'm not sure what changed, but it works. If anyone knows how this made a difference I would be glad to hear it. At least it works.

        Comment

        Working...