A Microsoft Office (Excel, Word) forum. OfficeFrustration

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » OfficeFrustration forum » Microsoft Access » Using Forms
Site Map Home Register Authors List Search Today's Posts Mark Forums Read  

#Name in fields



 
 
Thread Tools Display Modes
  #1  
Old August 12th, 2004, 03:03 PM
Design by Sue
external usenet poster
 
Posts: n/a
Default #Name in fields

I have two Access files given to me by a client. In the "Old" version all
fields work correctly, but in the "New" version, some of the fields have the
dredded #Name. These seem to be the fields with calculations involved, such
as =([expiration date]-Date()) and =[gallons]-[gallons used]. I have checked
all the properties and can not find any difference between the "Old" and
"New" Versions. Anyone have any ideas. I am not exceedingly knowledgable in
Access, but an not totally new to it either so any assistance would be
helpful.
  #2  
Old August 12th, 2004, 03:19 PM
Dib
external usenet poster
 
Posts: n/a
Default #Name in fields

Did you try the Date Diff

or try changing Date() with Now(). Format(Now(),"mm/dd/yyyy")
hope this helps


"Design by Sue" wrote in message
...
I have two Access files given to me by a client. In the "Old" version all
fields work correctly, but in the "New" version, some of the fields have

the
dredded #Name. These seem to be the fields with calculations involved,

such
as =([expiration date]-Date()) and =[gallons]-[gallons used]. I have

checked
all the properties and can not find any difference between the "Old" and
"New" Versions. Anyone have any ideas. I am not exceedingly knowledgable

in
Access, but an not totally new to it either so any assistance would be
helpful.



  #3  
Old August 12th, 2004, 04:09 PM
Design by Sue
external usenet poster
 
Posts: n/a
Default #Name in fields

Thanks Dib, but that didn't help. It seems to be bigger than the individual
field because there are 5 of them that don't work in the New version. I only
gave 2 examples. =IIf(Date()=[EXPIRATION DATE]-30,"NOTIFY CUSTOMER","") is
another. I have compared the tables and forms on both Old and New and can't
see any difference. If I copy the form from the Old to the New, and save it
as a different name, the copy works, but if I try to delete the original form
and save the new, copied one, as the original name, the corrected form
disappears. (found this out since my first post)
  #4  
Old August 12th, 2004, 04:23 PM
fredg
external usenet poster
 
Posts: n/a
Default #Name in fields

On Thu, 12 Aug 2004 07:03:03 -0700, Design by Sue wrote:

I have two Access files given to me by a client. In the "Old" version all
fields work correctly, but in the "New" version, some of the fields have the
dredded #Name. These seem to be the fields with calculations involved, such
as =([expiration date]-Date()) and =[gallons]-[gallons used]. I have checked
all the properties and can not find any difference between the "Old" and
"New" Versions. Anyone have any ideas. I am not exceedingly knowledgable in
Access, but an not totally new to it either so any assistance would be
helpful.


Things to consider when getting an #Error or #Name error in a
calculated control (not a complete list).

1) Is the name of the control the same as the name of any field used
in it's control source expression?

2) Are you absolutely sure that each field is spelled correctly?
[Expiration Date] is not the same as [ExpirationDate]

3) In your case, I suspect you have a missing reference, as this
example and the example on you later post both refer to the Date()
function.

Open any module in Design view (or click Ctrl + G).
On the Tools menu, click References.
Click to clear the check box for the type library or object library
marked as "Missing:."

An alternative to removing the reference is to restore the referenced
file to the path specified in the References dialog box. If the
referenced file is in a new location, clear the "Missing:" reference
and create a new reference to the file in its new folder.

See Microsoft KnowledgeBase articles:
283115 'ACC2002: References That You Must Set When You Work with
Microsoft Access'
Or for Access 97:
175484 'References to Set When Working With Microsoft Access' for
the correct ones needed,
and
160870 'VBA Functions Break in Database with Missing References' for
how to reset a missing one.

For even more information, see
http://members.rogers.com/douglas.j....nceErrors.html
--
Fred
Please only reply to this newsgroup.
I do not reply to personal email.
  #5  
Old August 12th, 2004, 05:19 PM
Design by Sue
external usenet poster
 
Posts: n/a
Default #Name in fields

Thanks fredg, but I'm a bit confused as to what you are telling me to do
(sorry - not that advanced - but I'm learning) These were written with the
Expression Builder. Control G gets me a blank window. When I checked the
References, nothing showed missing. I may not be getting what you are
saying, but if one version of the Database works and the other doesn't, with
the same programming, wouldn't that mean all of the References were there (I
may be asking a dumb question,but isn't the References referring to software
installed on the computer)
  #6  
Old August 12th, 2004, 05:37 PM
Design by Sue
external usenet poster
 
Posts: n/a
Default #Name in fields

Continuing on the References idea - I found the help file that refers to what
you were talking about fredg. It turns out I did it correctly from your
directions (thank you) but that the references are all ok. I also checked in
the Old version and found that they matched. Hope someone else has a clue.
  #7  
Old August 12th, 2004, 05:45 PM
Dib
external usenet poster
 
Posts: n/a
Default #Name in fields

When you create a database program, the programmer select (From the
Reference window) all the controls or dll's the program will be using.

so if then you create a blank database in a different version or same
version and Import all the Tables, Quries, Forms, Reports and Modules, you
still have to add the Reference manually. So to find out if any reference
are missing, open the old Version in the code window and lookup the
Reference that the program is using, if there are any then you will have to
manually add these References.



"Design by Sue" wrote in message
...
Thanks fredg, but I'm a bit confused as to what you are telling me to do
(sorry - not that advanced - but I'm learning) These were written with

the
Expression Builder. Control G gets me a blank window. When I checked the
References, nothing showed missing. I may not be getting what you are
saying, but if one version of the Database works and the other doesn't,

with
the same programming, wouldn't that mean all of the References were there

(I
may be asking a dumb question,but isn't the References referring to

software
installed on the computer)



  #8  
Old August 12th, 2004, 06:07 PM
Design by Sue
external usenet poster
 
Posts: n/a
Default #Name in fields

Thanks - I did check it against the Old Version, even did a screen shot and
compared them in Photoshop next to each other. There is no difference in the
References from Old to New. I also clicked though the entire list and all
References, even if not needed are present on my computer. I don't think
this is the problem. It is as if the functions (add, subtract etc) are not
working on the New version (hope that sparks some ideas)

  #9  
Old August 12th, 2004, 06:23 PM
Design by Sue
external usenet poster
 
Posts: n/a
Default #Name in fields

Just found another difference. In the From Properties on the Old, for filter
is shows (([COA Table].Comments Not Like "New Generation I*")) and in Order
By is shows [COA Table].[Customer Code]. I have tried to enter these into
the New Properties and it doesn't change anything.

Also, continuing to try to copy a version of the Old form to the New
version, I can do that as long as I keep the original (incorrect) form intact
and name the copied form a different name. If I delete the original form,
the copied form changes and will not work, as the original didn't. If I try
to save it as the same name as the original file, both disappear and there is
no form at all. The same happens if I delete the original file and change
the name of the copy to the original files name (all disappear)

This is getting so frustrating...I really want to figure it out, thanks for
all of your help!
  #10  
Old August 12th, 2004, 06:27 PM
Design by Sue
external usenet poster
 
Posts: n/a
Default #Name in fields

Oops that sould be Form Properties not Form Properties an dplease change the
"is" to "it" In short please forgive my typos!
 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
"UNION" Query with different fields in the two tables Dkline Running & Setting Up Queries 5 July 30th, 2004 09:05 PM
How to ignore fields in Update Query Casa Running & Setting Up Queries 6 July 12th, 2004 12:46 AM
Lost text fields in merge CGiannini General Discussion 5 June 4th, 2004 10:23 PM
Lookup fields on label report Howard Setting Up & Running Reports 1 June 3rd, 2004 02:43 AM
Calculating fields for Access Galin New Users 6 May 5th, 2004 12:05 AM


All times are GMT +1. The time now is 06:30 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 OfficeFrustration.
The comments are property of their posters.