Error in referencing files

[Klaus E. Frederiksen]

Hi

Just purchased the 'SyncfusionEssentialSuite' and we have some trouble with distribution of our app, or the SyncfusionEssentialSuite assemblies.

We have one central server form where all user starts our application. If a user needs some of the assemblies for our application, the missing assemblies are automaticly downloaded via HTTP.

When a user 'right click' on a tab, to get up the Context menu they get an error. See attached file for a detailed error log.

Now does the SyncfusionEssentialSuite loads some settings files or other data file when running or is there an simple explanation for our problems.

Regards

Klaus E. Frederiksen, Dangaaard Telecom IT, DK

[Administrator]

Hi,

No, during runtime, our assemblies are NOT being validated for license.

I suppose the exe that uses our assemblies and our assemblies are all in the same location, on a webserver? If so, the exe should be given "Full Trust" on the client's machine, so that the dependant assemblies also get "Full Trust".

Please let us know if this is not how your app is setup.

Could you also include Syncfusion.Shared.Design.dll in the same location as the other assemblies and check if that helps?

Please open a new support incident so we can handle this issue better.

Thanks
-Praveen Ramesh
Syncfusion, Inc.

> Hi
>
> Just purchased the 'SyncfusionEssentialSuite' and we have some trouble with distribution of our app, or the SyncfusionEssentialSuite assemblies.
>
> We have one central server form where all user starts our application. If a user needs some of the assemblies for our application, the missing assemblies are automaticly downloaded via HTTP.
>
> When a user 'right click' on a tab, to get up the Context menu they get an error. See attached file for a detailed error log.
>
> Now does the SyncfusionEssentialSuite loads some settings files or other data file when running or is there an simple explanation for our problems.
>
> Regards
>
> Klaus E. Frederiksen, Dangaaard Telecom IT, DK

[Rachel Gomez]

Access loads the pertinent file (for example, a type library, an object library, or a control library) for each reference, according to the information that is displayed in the References box. If Access cannot find the file, Access runs the following procedures to locate the file:

• Access checks to see whether the referenced file is currently loaded in memory.
  
• If the file is not loaded in memory, Access tries to verify that the RefLibPaths registry key exists. If the key exists, Access looks for a named value that has the same name as the reference. If there is a match, Access loads the reference from the path that the named value points to.
• Access then searches for the referenced file in the following locations, in this order:
• The Application folder (the location of the Msaccess.exe file).
• The current folder that you see if you click Open on the File menu.
• The Windows or Winnt folder where the operating system files are running.
• The System folder under the Windows or Winnt folder.
• The folders in the PATH environment variable that are directly accessible by the operating system.
• If Access cannot find the file, a reference error occurs.

Understanding reference error messages

• There are several error messages that relate to a missing file or to a file that has a different version from the version that is used in the database. In most cases, you can search the Microsoft Knowledge Base for an article about the specific error message, and you can then resolve the error by following the steps in the article. In some cases, a dependency file is not correctly matched with the primary file.

The following list describes some of the reference error messages that you may receive. However, note that the list does not include all of the possible reference error messages.

Typically, you may receive this error message if there is a problem with a programming type library, for example, an invalid Data Access Object (DAO) dynamic-link library (DLL) file. You can search the Microsoft Knowledge Base for articles that describe the various forms of this error message.

"Function is not available in Usage expression"

You may receive this error message if there is a problem with a programming type library, or if the code does not specifically call out the correct library and the file is listed at a lower priority in the reference list than a file that contains the same function name--for example, if DAO code is used with the ActiveX Data Object (ADO) library listed at a higher priority than the DAO library. You may also receive this error message if a form or a report contains an ActiveX control.

"Can't find project or library"

You may receive this error message if Access cannot locate a file in the reference list. Often the file is flagged asMissingin theReferencesdialog box. Sometimes the file exists on the development computer but not on the target computer.

"Variable not defined" or "User-defined type not defined"

You may receive one of these error messages if you use the User-Level Security Wizard to secure a database that references libraries other than the libraries that are included by default. For example, references to libraries that existed in the unsecured database are not automatically created in the new, secured database.

"Run-time error 5," "Invalid procedure call or argument," "The library which contains this symbol is not referenced by the current project," or "The library which contains this symbol is not referenced by the current project, so the symbol is undefined"

You may receive one of these error messages if there is a reference to a database, a type library, or an object library that is flagged asMissing.

"ActiveX component can't create object"

This error message does not necessarily mean that an ActiveX control is involved. For example, one possible cause is that DAO, which is an ActiveX component, cannot create an object because the DAO Automation Server cannot start. Frequently, the cause is that DLLs that provide referenced functionality for the program are not registered or are incorrectly registered.

Resolving reference issues on the development computer

Creating a new, blank database and then importing objects from another database file can create reference issues if the code or ActiveX controls rely on references that are not included in a database by default. The default references for an Access 2000 database are:

Visual Basic for Applications

• Microsoft Access 9.0 object library
• OLE Automation
• Microsoft ActiveX Data Objects (ADO) 2.1 library
• If the source is another Access 2000 database, verify that the references match. If the source is in an earlier version of Access, DAO 3.5 or earlier is probably in use; however, Access 2000 does not provide DAO 3.5 by default. Try removing the reference to the ADO 2.1 library (if it exists) and adding the reference to the DAO 3.6 object library.

If you converted the database from an earlier version of Access, and the database contains a reference to the Utility.mda file, in most cases you can remove this reference because the functions that this reference calls are included in the default references in Access 2000. If there are references to earlier versions of DAO, you can also remove these references because DAO 3.6 can address these functions.

To add a reference to a library:

• Open the database.
• Press ALT+F11 to start Visual Basic Editor.
• On the Tools menu, click References.
• Under Available References, click to select the check box next to the name of the library, and then click OK.

To remove a reference to a library:

• Open the database.
  
• Press ALT+F11 to start Visual Basic Editor.
• On the Tools menu, click References.
• Under Available References, click to clear the check box next to the name of the library, and then click OK.

Regards,

Rachel Gomez