Am I getting loopy or what?
OK, so am I getting loopy or what? Have a long standing procedure in Access 2000 that formats a postal code based on a country.
Format is '&#& #&#', which is used for Canada. It no longer seems to work.
Doing:
? Format$("L9T0K1","&#& #&#")
yields:
L#9 #T#0K1
Anyone else having issues all of a sudden with format? I'm wondering if an office or windows update has messed something up.
Jim.
Format is '&#& #&#', which is used for Canada. It no longer seems to work.
Doing:
? Format$("L9T0K1","&#& #&#")
yields:
L#9 #T#0K1
Anyone else having issues all of a sudden with format? I'm wondering if an office or windows update has messed something up.
Jim.
unknown_routine
How do you want the results of Format$("L9T0K1","&#& #&#") look?
ASKER
It's supposed to look like L9T 0K1
Format fills right to left, so the 1 should be the first #, K the first &, 0 the second #, and so on.
This routine has been in place for years and years and never had a problem. Now all of a sudden it does.
I'm seeing this on multiple machines, so either I missing something really obvious, or an update clobbered something.
Jim.
Format fills right to left, so the 1 should be the first #, K the first &, 0 the second #, and so on.
This routine has been in place for years and years and never had a problem. Now all of a sudden it does.
I'm seeing this on multiple machines, so either I missing something really obvious, or an update clobbered something.
Jim.
jim,
i get the same result.
Canada postal code format is L9T 0K1
try something like format("L9T0K1","@@@ @@@")
i get the same result.
Canada postal code format is L9T 0K1
try something like format("L9T0K1","@@@ @@@")
Alright, Jim. I'll ask all the basic questions?
Office/Access Version?
OS? (patch/update)?
There was some discussion about a week ago (maybe longer) about an Office update that caused a bunch of havoc with several Access things. Don't remember what version it applied to but I think the fix was to restore the pre-update version.
Dale
Office/Access Version?
OS? (patch/update)?
There was some discussion about a week ago (maybe longer) about an Office update that caused a bunch of havoc with several Access things. Don't remember what version it applied to but I think the fix was to restore the pre-update version.
Dale
ASKER
@Dale,
<<Alright, Jim. I'll ask all the basic questions?>>
<<Don't remember what version it applied to but I think the fix was to restore the pre-update version.>>
I'll have to start digging...for the moment, I was looking for agreement that the format should work as stated (that's partly why the title of the question).
Second was to see if anyone else was having format issues.
@Cap
<<try something like format("L9T0K1","@@@ @@@") >>
Already did last night at 1:30 am<g>, which does work for now. No real reason I can't keep it that way that I can think of, but I loath to change something so fundamental to the application that has been in place for eight years and working fine.
My main goal is to understand why all of a sudden this failed. A Office/Windows update is the only thing I can think of.
Guess I should have stated up front that the question is more about:
1. Confirming there is a problem.
2. And if so, serveing as a warning to be on the lookout for this.
I'd love to have someone check this on a machine that doesn't get patched often. I don't have any machines here that are not on automatic update.
Ah wait, there's an old laptop here! I'll give that a go.
Jim.
<<Alright, Jim. I'll ask all the basic questions?>>
<<Don't remember what version it applied to but I think the fix was to restore the pre-update version.>>
I'll have to start digging...for the moment, I was looking for agreement that the format should work as stated (that's partly why the title of the question).
Second was to see if anyone else was having format issues.
@Cap
<<try something like format("L9T0K1","@@@ @@@") >>
Already did last night at 1:30 am<g>, which does work for now. No real reason I can't keep it that way that I can think of, but I loath to change something so fundamental to the application that has been in place for eight years and working fine.
My main goal is to understand why all of a sudden this failed. A Office/Windows update is the only thing I can think of.
Guess I should have stated up front that the question is more about:
1. Confirming there is a problem.
2. And if so, serveing as a warning to be on the lookout for this.
I'd love to have someone check this on a machine that doesn't get patched often. I don't have any machines here that are not on automatic update.
Ah wait, there's an old laptop here! I'll give that a go.
Jim.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for checking.
Jim.
Jim.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.