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

Impact of changing field property in Table

P: n/a
Hi:

I am having a problem making the impact a field property change in a table trickle through
to a report. Between the table and the report are numerous queries and sums. I have
changed the field definition from Text to Numeric (single), so that formatting can be done
more efefctivlet, but somwhow the report doesnt recognize that change.

Do I have to change each query and reference to the field, or is the impact supposed to go
through automatically?.

Regards

John Baker

Nov 12 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
The data type of calculated field are often misunderstood in Access.

For suggestions on how to avoid this, see:
http://allenbrowne.com/ser-45.html

--
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.

"John Baker" <Ba******@Verizon.net> wrote in message
news:k6********************************@4ax.com...
Hi:

I am having a problem making the impact a field property change in a table trickle through to a report. Between the table and the report are numerous queries and sums. I have changed the field definition from Text to Numeric (single), so that formatting can be done more efefctivlet, but somwhow the report doesnt recognize that change.

Do I have to change each query and reference to the field, or is the impact supposed to go through automatically?.

Regards

John Baker

Nov 12 '05 #2

P: n/a
Thanks for the tip.

My help file is only partially functional. Could you possibly tell me the correct command
to convert a test field into a numeric field that can accept decimals? I somehow ended up
with text in one of my fields that should have been numeric, and cant set it as fixed
decimal on a report.

Thanks again

John Baker

"Allen Browne" <Al*********@SeeSig.Invalid> wrote:
The data type of calculated field are often misunderstood in Access.

For suggestions on how to avoid this, see:
http://allenbrowne.com/ser-45.html


Nov 12 '05 #3

P: n/a
Val() or CDbl()

--
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.

"John Baker" <Ba******@Verizon.net> wrote in message
news:b6********************************@4ax.com...
Thanks for the tip.

My help file is only partially functional. Could you possibly tell me the correct command to convert a test field into a numeric field that can accept decimals? I somehow ended up with text in one of my fields that should have been numeric, and cant set it as fixed decimal on a report.

Thanks again

John Baker

"Allen Browne" <Al*********@SeeSig.Invalid> wrote:
The data type of calculated field are often misunderstood in Access.

For suggestions on how to avoid this, see:
http://allenbrowne.com/ser-45.html

Nov 12 '05 #4

P: n/a
Thanks

"Allen Browne" <Al*********@SeeSig.Invalid> wrote:
Val() or CDbl()


Nov 12 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.