I have a form that has a date field that, on opening defaults to Date()
it works perfectly with Access 2000, 2002, 2003, but with some versions of
Access 2007 I get #name in the field - it seems to be more prevalent on Vista

Most likely, the References in the 2007 database are "messed up". Likely
causes include using early binding in your VBA code.

Try following these steps (from a post by Douglas Steele, MVP):

This can be caused by differences in either the location or file version of
certain files between the machine where the application was developed, and
where it's being run (or the file missing completely from the target
machine). Such differences are common when new software is installed.

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://members.rogers.com/douglas.j....nceErrors.html

--

Ken Snell
<MS ACCESS MVP>
http://www.accessmvp.com/KDSnell/


"DAve" <(E-Mail Removed)> wrote in message
news:88435264-3D48-4525-9B3F-(E-Mail Removed)...
>I have a form that has a date field that, on opening defaults to Date()
> it works perfectly with Access 2000, 2002, 2003, but with some versions of
> Access 2007 I get #name in the field - it seems to be more prevalent on
> Vista

Hi Ken

Thanks for that - I don't believe its a reference issue. We have many
copies running on various machines and are aware of references and related
issues

It seems to be a problem on some (not all) Vista machines running Access 2007.

What we have noticed is that the machine we are currently having an issue
with only has Vista SP1 applied - not sure if that would make any difference
- are you aware of any compatibility issues with SP1?

What we have found is that a Access 2k mdb complied on a Vista SP2 machine
works fine on the SP1 machine, but the same mde does not (having said that
the mde was created (not complied) on XP - any suggestion most welcome.

Dave

I'm not familiar with any such bug / problem, but let me ask others.

--

Ken Snell
<MS ACCESS MVP>
http://www.accessmvp.com/KDSnell/


"DAve" <(E-Mail Removed)> wrote in message
news:B8E8B051-7C32-420E-BD38-(E-Mail Removed)...
> Hi Ken
>
> Thanks for that - I don't believe its a reference issue. We have many
> copies running on various machines and are aware of references and related
> issues
>
> It seems to be a problem on some (not all) Vista machines running Access
> 2007.
>
> What we have noticed is that the machine we are currently having an issue
> with only has Vista SP1 applied - not sure if that would make any
> difference
> - are you aware of any compatibility issues with SP1?
>
> What we have found is that a Access 2k mdb complied on a Vista SP2 machine
> works fine on the SP1 machine, but the same mde does not (having said that
> the mde was created (not complied) on XP - any suggestion most welcome.
>
> Dave
>

Access 2007 will give problems if it does not have SP2 for Access 2007.
Maybe this is the issue with some of your computer.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia


"Ken Snell MVP" <(E-Mail Removed)> wrote in message
news:O%(E-Mail Removed)...
> I'm not familiar with any such bug / problem, but let me ask others.
>
> --
>
> Ken Snell
> <MS ACCESS MVP>
> http://www.accessmvp.com/KDSnell/
>
>
> "DAve" <(E-Mail Removed)> wrote in message
> news:B8E8B051-7C32-420E-BD38-(E-Mail Removed)...
>> Hi Ken
>>
>> Thanks for that - I don't believe its a reference issue. We have many
>> copies running on various machines and are aware of references and
>> related
>> issues
>>
>> It seems to be a problem on some (not all) Vista machines running Access
>> 2007.
>>
>> What we have noticed is that the machine we are currently having an issue
>> with only has Vista SP1 applied - not sure if that would make any
>> difference
>> - are you aware of any compatibility issues with SP1?
>>
>> What we have found is that a Access 2k mdb complied on a Vista SP2
>> machine
>> works fine on the SP1 machine, but the same mde does not (having said
>> that
>> the mde was created (not complied) on XP - any suggestion most welcome.
>>
>> Dave
>>
>
>

Hi Jeanette

Thanks for that - just to clarify

Do you mean SP2 for Access 2007 or SP2 for Vista?

I mean sp2 for access - really office 2007. That is completely different
from sp2 for vista.


Jeanette Cunningham MS Access MVP -- Melbourne Victoria Australia

"DAve" <(E-Mail Removed)> wrote in message
news:79D4D993-BC1B-45A4-99F7-(E-Mail Removed)...
> Hi Jeanette
>
> Thanks for that - just to clarify
>
> Do you mean SP2 for Access 2007 or SP2 for Vista?

Try recompiling the ACCESS VBA code in the .mdb file on the VISTA SP1
machine.

--

Ken Snell
<MS ACCESS MVP>
http://www.accessmvp.com/KDSnell/


"Ken Snell MVP" <(E-Mail Removed)> wrote in message
news:O%(E-Mail Removed)...
> I'm not familiar with any such bug / problem, but let me ask others.
>
> --
>
> Ken Snell
> <MS ACCESS MVP>
> http://www.accessmvp.com/KDSnell/
>
>
> "DAve" <(E-Mail Removed)> wrote in message
> news:B8E8B051-7C32-420E-BD38-(E-Mail Removed)...
>> Hi Ken
>>
>> Thanks for that - I don't believe its a reference issue. We have many
>> copies running on various machines and are aware of references and
>> related
>> issues
>>
>> It seems to be a problem on some (not all) Vista machines running Access
>> 2007.
>>
>> What we have noticed is that the machine we are currently having an issue
>> with only has Vista SP1 applied - not sure if that would make any
>> difference
>> - are you aware of any compatibility issues with SP1?
>>
>> What we have found is that a Access 2k mdb complied on a Vista SP2
>> machine
>> works fine on the SP1 machine, but the same mde does not (having said
>> that
>> the mde was created (not complied) on XP - any suggestion most welcome.
>>
>> Dave
>>
>
>

DAve <(E-Mail Removed)> wrote:

>Thanks for that - I don't believe its a reference issue. We have many
>copies running on various machines and are aware of references and related
>issues

Just to double check though could you run the following code and
report back?

Sub ViewReferenceDetails()

Dim ref As Reference

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

End Sub

Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
Granite Fleet Manager http://www.granitefleet.com/

Hi All

Thanks for all your helpfull suggestions - we have found that upgrading the
Vista machine to SP2 solved this, obviously some compatibility bug with Vista
SP1 & Access 07

Dave