Results 1 to 8 of 8
  1. #1
    New Lounger
    Join Date
    May 2003
    Location
    Baltimore, Maryland, USA
    Posts
    10
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Error Number 3320 (Access 2002)

    On some machines on which I install an .mde I receive an error "Function is not available in expressions in table-level validation expression", but on some machines it runs without issue. I'm using the Packaging Wizard with the run time version of AXP to set up on machines without Access.

    Any suggestions would be appreciated.

  2. #2
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Error Number 3320 (Access 2002)

    That sounds like one of the references is not valid on some of the target machines. Unfortunately, you can't test interactively since the machines don't have the full version of Access (and you can't view modules in an .MDE anyway.)

    Does the .MDB database you created the .MDE from use controls that are not native to Access? If so, you must take care to install the corresponding file(s). And does it have references to other apps, such as Word, Excel or Outlook? If so, do the target machines have the same versions of these apps?

  3. #3
    New Lounger
    Join Date
    May 2003
    Location
    Baltimore, Maryland, USA
    Posts
    10
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Error Number 3320 (Access 2002)

    Thank you, sir.

    I am using the Common Dialog control to browse for files, so that might be it.

    I am exporting data in an .xls format, but I don't actually call Excel, merely use the TransferSpreadsheet method, so I would not expect that to be the issue.

    How do I determine the name(s) of the additional file(s) to include in the package, based upon the control?

  4. #4
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Error Number 3320 (Access 2002)

    If you activate the Visual Basic Editor in the MDB, and select Tools | References..., you'll probably see a reference to the Microsoft Common Dialog Control 6.0. If you select it, you will see the corresponding filename will be in the lower half of the dialog. On my system, it is C:WindowsSystem32Comdlg32.ocx.

    By the way, Access 2002 has a built-in FileDialog. This only works in Access 2002 and up, not in Access 2000 or earlier. In all versions of Access, you can display the Open or Save as dialog using Windows API calls without needing to distribute a file or setting a reference. See for example <post#=297358>post 297358</post#>.

  5. #5
    New Lounger
    Join Date
    May 2003
    Location
    Baltimore, Maryland, USA
    Posts
    10
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Error Number 3320 (Access 2002)

    Thank you again.

    Forgive me for being obtuse, but I expected the Packaging Wizard to identify the dependencies, and include the files. Is there a setting I can control which will force the process?

  6. #6
    Plutonium Lounger
    Join Date
    Mar 2002
    Posts
    84,353
    Thanks
    0
    Thanked 29 Times in 29 Posts

    Re: Error Number 3320 (Access 2002)

    I'm sorry, others will have to answer that question.

  7. #7
    Super Moderator
    Join Date
    Aug 2001
    Location
    Evergreen, CO, USA
    Posts
    6,623
    Thanks
    3
    Thanked 60 Times in 60 Posts

    Re: Error Number 3320 (Access 2002)

    In general the Packaging wizard in Office XP Developer will identify what files are necessary and include them. If however you are creating .mde files, then the workstation is expected to have whatever objects (ocxs, dlls, etc.) are referenced. An .mde simply removes the VBA source statements and locks forms and reports.
    Wendell

  8. #8
    New Lounger
    Join Date
    May 2003
    Location
    Baltimore, Maryland, USA
    Posts
    10
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Error Number 3320 (Access 2002)

    Thank you, I did not anticipate that MDEs would be treated differently from MDBs. Once I manually inserted the dependent files, I have not had a recurrence of the problem.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •