2007 Runtime Problems

[J Krukonis]

I have a 2003 database that has been converted to 2007 and all code compiled.
All references are intact. It is fully functional as an .ACCDB using both
access 2007 and runtime 2007.

When converted to an ACCDE, the following errors appear: Function is not
available in expressions in query expressions (Function Expression). Both in
Access 2007 and runtime 2007.

If I build a package and install as an .ACCDR, all functionality is
restored. Since this application is constantly changing and is used by a
multitude of people this deployment is not possible.

Does anyone know how to create an .ACCDR without going through the package
deployment process? or How to resolve the issue with an .ACCDE file?

Thanks

 

[J Krukonis]

Here's more info. Runtime 2007 also gives the "Function is not

 

[Tony Toews [MVP]]

I have a 2003 database that has been converted to 2007 and all code compiled.
All references are intact. It is fully functional as an .ACCDB using both
access 2007 and runtime 2007.

When converted to an ACCDE, the following errors appear: Function is not
available in expressions in query expressions (Function Expression). Both in
Access 2007 and runtime 2007.

This sure looks like a references problem. Try running the following
code in a module and let us know what it finds.

Sub DebugPrintReferences
Dim ref As Reference

For Each ref In Access.References
Debug.Print ref.Name & " " & ref.FullPath & " " & ref.Major &
"." & ref.Minor
Next ref

end sub

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[J Krukonis]

Here are the results on the developer machine (which is running both Access
2003 and 2007). I only ran the code for v2003, since that is the native
format of the application.

VBA C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL 4.0
Access C:\Program Files\Microsoft Office\OFFICE11\msacc.olb 9.0
DAO C:\WINDOWS\system32\dao360.dll 5.0
MSComctlLib C:\WINDOWS\system32\Mscomctl.ocx 2.0
stdole C:\WINDOWS\system32\STDOLE2.TLB 2.0
VBIDE C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6EXT.OLB 5.3
OWC10 C:\Program Files\Common Files\Microsoft Shared\Web
Components\10\OWC10.DLL 1.1
MSACAL C:\PROGRA~1\MICROS~2\OFFICE11\MSCAL.OCX 7.0
MSComCtl2 C:\WINDOWS\system32\Mscomct2.ocx 2.0

Thanks
Jeff

 

[Tony Toews [MVP]]

Here are the results on the developer machine (which is running both Access
2003 and 2007). I only ran the code for v2003, since that is the native
format of the application.

VBA C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL 4.0
Access C:\Program Files\Microsoft Office\OFFICE11\msacc.olb 9.0
DAO C:\WINDOWS\system32\dao360.dll 5.0
stdole C:\WINDOWS\system32\STDOLE2.TLB 2.0

Above are reasonable.

MSComctlLib C:\WINDOWS\system32\Mscomctl.ocx 2.0
VBIDE C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6EXT.OLB 5.3
OWC10 C:\Program Files\Common Files\Microsoft Shared\Web
Components\10\OWC10.DLL 1.1
MSACAL C:\PROGRA~1\MICROS~2\OFFICE11\MSCAL.OCX 7.0
MSComCtl2 C:\WINDOWS\system32\Mscomct2.ocx 2.0

The above are likely not needed. I'd suggest unchecking them one at
a time and recompiling your VBA code to see if there's a problem.

Now the MSCal is probably being used. However we strongly urge folks
to replace it with a form or API call.

See the Calendar Tips page at my website
http://www.granite.ab.ca/access/calendars.htm

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[J Krukonis]

Tony,

that seems to work. will keep you posted.

on a similar issue, all my .mde file are set to "Compact on Close". the
temp "database" and "db1" files are not being deleted when opened using
access 2007. all users have modify rights to the network folders where these
temp files are being created. do they need full control?

Thanks
Jeff

 

[Tony Toews [MVP]]

that seems to work. will keep you posted.

on a similar issue, all my .mde file are set to "Compact on Close". the
temp "database" and "db1" files are not being deleted when opened using
access 2007. all users have modify rights to the network folders where these
temp files are being created. do they need full control?

I never use Compact on Close. MDE files will grow a small amount
during usage but I've had clients that haven't touched theirs for
years.

That said the users will need delete permissions also.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/