By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,836 Members | 2,018 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,836 IT Pros & Developers. It's quick & easy.

Access 2007 runtime problem

P: n/a
Hi,

On a machine running Vista I have just converted an A2003 application
to A2007, built an MSI package for it and installed it on my kid's PC,
which is running Windows XP and A2003.

I installed the A2007 runtime first, then my application. However,
when I open my application, the system Data and Time are both showing
as #Name. Any ideas?

Reg

Oct 25 '07 #1
Share this Question
Share on Google+
5 Replies


P: n/a
"Reg (Lincolnshire)" <re*@solutionj.co.ukwrote:
>On a machine running Vista I have just converted an A2003 application
to A2007, built an MSI package for it and installed it on my kid's PC,
which is running Windows XP and A2003.

I installed the A2007 runtime first, then my application. However,
when I open my application, the system Data and Time are both showing
as #Name. Any ideas?
Sounds like a references problem.

Do you have any references besides the basic three or four? Are you sure you need
them? Write down the path and name of the extra ones (or put the following code in a
module and execute the code), delete from the references list and Compile and Save
All. Keep any necessary references and ensure they are distributed to the target
system.

Dim ref As Reference

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

For a very detailed page on reference problems see
http://www.accessmvp.com/djsteele/Ac...nceErrors.html

Ctrl+G will take you into the Debug/Immediate window. Then click on
Tools on the menu bar and References.

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/
Oct 27 '07 #2

P: n/a
On Oct 27, 2:45 am, "Tony Toews [MVP]" <tto...@telusplanet.netwrote:
"Reg (Lincolnshire)" <r...@solutionj.co.ukwrote:
On a machine running Vista I have just converted an A2003 application
to A2007, built an MSI package for it and installed it on my kid's PC,
which is running Windows XP and A2003.
I installed the A2007 runtime first, then my application. However,
when I open my application, the system Data and Time are both showing
as #Name. Any ideas?

Sounds like a references problem.

Do you have any references besides the basic three or four? Are you sure you need
them? Write down the path and name of the extra ones (or put the following code in a
module and execute the code), delete from the references list and Compile and Save
All. Keep any necessary references and ensure they are distributed to the target
system.

Dim ref As Reference

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

For a very detailed page on reference problems seehttp://www.accessmvp.com/djsteele/AccessReferenceErrors.html

Ctrl+G will take you into the Debug/Immediate window. Then click on
Tools on the menu bar and References.

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 athttp://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
Thanks for this. I pinned down the culprit as being MSADOX.DLL. It
looks like the problem is that I am developing the system on a machine
running Vista (and therefore Windows DAC) but deploying it onto
machines running XP (MDAC).

I was using ADOX to add new columns to my BE databese etc, so for now
I've commented out that code, removed the reference and it works -
well, at least that problem is solved. Looks like I will have to
switch to using SQL commands to manipulate tables from now on.

Thanks for coming back to me.
Reg

Oct 27 '07 #3

P: n/a
"Reg (Lincolnshire)" <re*@solutionj.co.ukwrote:
>Thanks for this. I pinned down the culprit as being MSADOX.DLL. It
looks like the problem is that I am developing the system on a machine
running Vista (and therefore Windows DAC) but deploying it onto
machines running XP (MDAC).
Now isn't that interesting.
>I was using ADOX to add new columns to my BE databese etc, so for now
I've commented out that code, removed the reference and it works -
well, at least that problem is solved. Looks like I will have to
switch to using SQL commands to manipulate tables from now on.
Nah, DAO can do that very nicely as well and has a lot more functionality. See the
TempTables.MDB page at my website which illustrates how to use a temporary MDB in
your app. http://www.granite.ab.ca/access/temptables.htm

See http://home.gci.net/~mike-noel/Compa.../CompareEM.htm for a decent,
although not perfect tool.

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/
Oct 27 '07 #4

P: n/a
On Oct 27, 3:49 pm, "Tony Toews [MVP]" <tto...@telusplanet.netwrote:
"Reg (Lincolnshire)" <r...@solutionj.co.ukwrote:
Thanks for this. I pinned down the culprit as being MSADOX.DLL. It
looks like the problem is that I am developing the system on a machine
running Vista (and therefore Windows DAC) but deploying it onto
machines running XP (MDAC).

Now isn't that interesting.
I was using ADOX to add new columns to my BE databese etc, so for now
I've commented out that code, removed the reference and it works -
well, at least that problem is solved. Looks like I will have to
switch to using SQL commands to manipulate tables from now on.

Nah, DAO can do that very nicely as well and has a lot more functionality. See the
TempTables.MDB page at my website which illustrates how to use a temporary MDB in
your app.http://www.granite.ab.ca/access/temptables.htm

Seehttp://home.gci.net/~mike-noel/CompareEM-LITE/CompareEM.htmfor a decent,
although not perfect tool.

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 athttp://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog -http://msmvps.com/blogs/access/
Tony,

Re your "now isn't that interesting" comment. Could you expand please?
Surely i'm not the first person to have this issue?

Oct 28 '07 #5

P: n/a
"Reg (Lincolnshire)" <re*@solutionj.co.ukwrote:
>"Reg (Lincolnshire)" <r...@solutionj.co.ukwrote:
>Thanks for this. I pinned down the culprit as being MSADOX.DLL. It
looks like the problem is that I am developing the system on a machine
running Vista (and therefore Windows DAC) but deploying it onto
machines running XP (MDAC).

Now isn't that interesting.

Re your "now isn't that interesting" comment. Could you expand please?
Surely i'm not the first person to have this issue?
I have no idea as I seldom use ADO except at one client site and have no real
exxperience with MDAC. And the more comments like yours I read make me quite happy
that I've stuck with DAO. <smile>

I'd suggest starting a new thread with MDAC being part of the subject.

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/
Oct 29 '07 #6

This discussion thread is closed

Replies have been disabled for this discussion.