Table Format Property > not recognized cuasing no data to be displ

[Guest]

I have been running a MsAccess appication on our office network for over 2
years now with no issues.

The MsAccess .mde file is accessed by multiple people in the company and
this issue is only happening only on one PC which leads me to believe it may
be a corrupt driver or currpot DLL. When running the application MsAccess
does not report any error or any execution faults.

PC Details - Windows XP SP 3
Software - MsAccess 2003 SP 3

Problem Overview -

I have created a table and defined some fields names (i.e customer) where
the data type = text. I want the user to enter some text and when the data is
saved to the table I want it to be stored in all caps format regardless of
the users entry (caps on or off).

For this to occur I am using the FORMAT property of the field name and
setting it to ">" to resolve this formating entry issue. THis forces the data
entry to be saved in caps.

Running in form view:
If use a lookup table to call up the customer data, the resultant indicates
that the data for the customer field is blank.

If I remove the ">" in the FORMAT property for the customer field name, and
then use the same lookup table then I am able to see the customer data.

All the fields in my table that have the FORMAT property set to ">" is
causing the same thing. MsAccess in form view mode will not display the data.

This syntax of setting the formet property to ">" has worked in the past in
the same application and is working on other XP machines running MsAccess
2003 SP3.

THis is why I am assuming it has something to do with my pc where a file
that is used by MsAccess is missing or currupt.

Note: It seems to be only a display issue because if you i.e.. add a new
lookup table (form edit/ design mode) and point it to the table, CUSTOMERS
column, you can see all the data. As soon as you go out of the DESIGN mode
into VIEW mode, and use the lookup button, no data is displayed.

Any thought on what could be causing this display problem?

Rgs,
M.Moro

 

[Guest]

see in line comments below
--
Dave Hargis, Microsoft Access MVP

I have been running a MsAccess appication on our office network for over 2
years now with no issues.

The MsAccess .mde file is accessed by multiple people in the company and
this issue is only happening only on one PC which leads me to believe it may
be a corrupt driver or currpot DLL. When running the application MsAccess
does not report any error or any execution faults.

Each user should have their own copy of the mde on their own computer. You
are reducing performance and may have corruption problems with this model.
It is also a big hit on network traffic.

PC Details - Windows XP SP 3
Software - MsAccess 2003 SP 3

Problem Overview -

I have created a table and defined some fields names (i.e customer) where
the data type = text. I want the user to enter some text and when the data is
saved to the table I want it to be stored in all caps format regardless of
the users entry (caps on or off).

For this to occur I am using the FORMAT property of the field name and
setting it to ">" to resolve this formating entry issue. THis forces the data
entry to be saved in caps.

The format property has no effect on how data is store, only how it is
displayed.

Running in form view:
If use a lookup table to call up the customer data, the resultant indicates
that the data for the customer field is blank.

If I remove the ">" in the FORMAT property for the customer field name, and
then use the same lookup table then I am able to see the customer data.

All the fields in my table that have the FORMAT property set to ">" is
causing the same thing. MsAccess in form view mode will not display the data.

This syntax of setting the formet property to ">" has worked in the past in
the same application and is working on other XP machines running MsAccess
2003 SP3.

THis is why I am assuming it has something to do with my pc where a file
that is used by MsAccess is missing or currupt.

Remember what I said about corruption earlier?

 

[Guest]

Thanks for the quick response.

In the design mode if you create a look up box and set the format property
to ">", then I agree regardless of how the data is saved in the table it
would be display the resultant in caps.

If you set the format property for the field name at the table properties
level, then regardless of how the alpha characters are entered when the data
is saved to the table it forces it to caps format.

This does not still explain why in the VIEW mode the data is not displayed.

To ensure it was not a currupt table I quickly made another application with
one table and one form with a lookup. Same thing.

 

[George Nicholson]

I think the problem you are seeing is a known (but yet to be acknowledged by
Redmond) bug introduced by SP3. I'm pretty sure you are not the first to
report it in the last few weeks. I would search the posts to see what the
suggested work arounds (if any) are.

HTH,

 

[Guest]

THanks George for the suggestion.

Unfortunitely you can not unistall a Office SP so I had to remove Office
2003 and re-install. Applied the SP 2 update and tried the MsAccess
application and it worked.

SO this basically confirms that the there is a issue with MsOffice 2003 SP3.

Hope this helps other users with the same issue.

Rgs,
M.Moro