References problem - new variant

[Jim Devenish]

I am familiar with the issue of missing references but I have a
situation that is new to me.

I have a split fe/be system. A copy of the fe is on the server which
is then copied to each user's PC using AutoFE. This has worked well
for some years. However on one PC when the fe is copied to that PC,
it fails to compile with the usual message:
"Can't find project or library". When I open the References window
NONE are marked as Missing. If I click OK (but not Cancel) and then
Compile everything works OK.

Clearly all the references are correct and the required files exist in
the right place. It would seem that simply opening the References
window and then closing it enables the program to find them
correctly. I cannot expect the user to do this every time I issue a
new version of the fe.

On other PCs with the same version of Access and the same files,
everything works correctly.

Has anyone come across this problem? If so, any advice would be
welcome.

Please do not suggest late binding and removing references.

Jim

[Allen Browne]

Jim, I suspect that there is an issue with one of the libraries on that
machine.

Sometimes no libraries show as missing.
But you can solve the problem with:
1. Remove the reference in the database.
2. Unregister the library (with regsvr32 -u).
3. Register it again.
4. Open the database and add the reference again.

If you're not sure how to do that, see:
http://allenbrowne.com/ser-38.html

If that's not the issue, what version of Access, what service pack, and what
version of Windows? Particularly the virtualization of folders under Vista
can be problematic under different users.

--
Allen Browne - Microsoft MVP. Perth, Western Australia
Tips for Access users - http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jim Devenish" <in***************@foobox.comwrote in message
news:e1**********************************@c23g2000 hsa.googlegroups.com...

>I am familiar with the issue of missing references but I have a
situation that is new to me.

I have a split fe/be system. A copy of the fe is on the server which
is then copied to each user's PC using AutoFE. This has worked well
for some years. However on one PC when the fe is copied to that PC,
it fails to compile with the usual message:
"Can't find project or library". When I open the References window
NONE are marked as Missing. If I click OK (but not Cancel) and then
Compile everything works OK.

Clearly all the references are correct and the required files exist in
the right place. It would seem that simply opening the References
window and then closing it enables the program to find them
correctly. I cannot expect the user to do this every time I issue a
new version of the fe.

On other PCs with the same version of Access and the same files,
everything works correctly.

Has anyone come across this problem? If so, any advice would be
welcome.

Please do not suggest late binding and removing references.

Jim

[Jim Devenish]

On Jan 17, 11:24*am, "Allen Browne" <[e-mail]>
wrote:

Jim, I suspect that there is an issue with one of the libraries on that
machine.

Sometimes no libraries show as missing.
But you can solve the problem with:
1. Remove the reference in the database.
2. Unregister the library (with regsvr32 -u).
3. Register it again.
4. Open the database and add the reference again.

If you're not sure how to do that, see:
* *http://allenbrowne.com/ser-38.html

If that's not the issue, what version of Access, what service pack, and what
version of Windows? Particularly the virtualization of folders under Vista
can be problematic under different users.

--
Allen Browne - Microsoft MVP. *Perth, Western Australia
Tips for Access users -http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.

"Jim Devenish" <[e-mail] in message

news:e1**********************************@c23g2000 hsa.googlegroups.com...

I am familiar with the issue of missing references but I have a
situation that is new to me.

I have a split fe/be system. *A copy of the fe is on the server which
is then copied to each user's PC using AutoFE. *This has worked well
for some years. *However on one PC when the fe is copied to that PC,
it fails to compile with the usual message:
"Can't find project or library". *When I open the References window
NONE are marked as Missing. *If I click OK (but not Cancel) and then
Compile everything works OK.

Clearly all the references are correct and the required files exist in
the right place. *It would seem that simply opening the References
window and then closing it enables the program to find them
correctly. *I cannot expect the user to do this every time I issue a
new version of the fe.

On other PCs with the same version of Access and the same files,
everything works correctly.

Has anyone come across this problem? *If so, any advice would be
welcome.

Please do not suggest late binding and removing references.

Jim

Thank you Allen. That offers some promise. I will give it try.

Jim

[Steve Brown]

I've heard of this when the office files were located in a
different location.

(david)

"Jim Devenish" <in***************@foobox.comwrote in message
news:e1**********************************@c23g2000 hsa.googlegroups.com...

>I am familiar with the issue of missing references but I have a
situation that is new to me.

I have a split fe/be system. A copy of the fe is on the server which
is then copied to each user's PC using AutoFE. This has worked well
for some years. However on one PC when the fe is copied to that PC,
it fails to compile with the usual message:
"Can't find project or library". When I open the References window
NONE are marked as Missing. If I click OK (but not Cancel) and then
Compile everything works OK.

Clearly all the references are correct and the required files exist in
the right place. It would seem that simply opening the References
window and then closing it enables the program to find them
correctly. I cannot expect the user to do this every time I issue a
new version of the fe.

On other PCs with the same version of Access and the same files,
everything works correctly.

Has anyone come across this problem? If so, any advice would be
welcome.

Please do not suggest late binding and removing references.

Jim