I watched this chap today have a mailmerge problem. He had a spreadsheet with
say 30 rows, one column of which was supposed to contain dates in UK format,
such as 21/2/23 for today. When he used the date column to merge into the Word
doc, the dates kept coming out in the merged doc as 2/21/23, US style.

I made these suggestions:

1) Check the Word doc has UK English set as language.
2) Check that the locale for the machine was UK date style and UK English.
3) In the Excel SS, set the column to have a custom date format dd-mmm-yyyy
[1]
4) In the machine Settings, US English semed to be above UK English, so we
fixed that and he logged out/in.

But: whatever we did, the date field in the merged Word doc always showed the
date as mm/dd/yy.

Any suggestions for how to make the merged field in the Word doc contain the
date in the same format as in the Excel SS would be most welcome.

[1] Oddly, when we did this, some dates showed as dd-mmm-yyyy in that SS
column, but some continued to show as dd/mm/yy.
--
Tim

On 21/02/2023 21:52, Tim Streater wrote:
> I watched this chap today have a mailmerge problem. He had a spreadsheet with
> say 30 rows, one column of which was supposed to contain dates in UK format,
> such as 21/2/23 for today. When he used the date column to merge into the Word
> doc, the dates kept coming out in the merged doc as 2/21/23, US style.
>
> I made these suggestions:
>
> 1) Check the Word doc has UK English set as language.
> 2) Check that the locale for the machine was UK date style and UK English.
> 3) In the Excel SS, set the column to have a custom date format dd-mmm-yyyy
> [1]
> 4) In the machine Settings, US English semed to be above UK English, so we
> fixed that and he logged out/in.
>
> But: whatever we did, the date field in the merged Word doc always showed the
> date as mm/dd/yy.
>
> Any suggestions for how to make the merged field in the Word doc contain the
> date in the same format as in the Excel SS would be most welcome.
>
>
> [1] Oddly, when we did this, some dates showed as dd-mmm-yyyy in that SS
> column, but some continued to show as dd/mm/yy.

Dunno, but a possible workaround may be to have three date fields
instead of one. You can use formulae in Excel to create 3 columns - one
for day, one for month and one for year. You can then use the mail-merge
to control how those 3 fields appear in the Word document.
Or, if you only want one field, create a text string in Excel with the
date in your chosen format, and use that in the mail merge.
--
Cheers,
Roger

On 21/02/2023 21:52, Tim Streater wrote:
> I watched this chap today have a mailmerge problem. He had a spreadsheet with
> say 30 rows, one column of which was supposed to contain dates in UK format,
> such as 21/2/23 for today. When he used the date column to merge into the Word
> doc, the dates kept coming out in the merged doc as 2/21/23, US style.
>
> I made these suggestions:
>
> 1) Check the Word doc has UK English set as language.
> 2) Check that the locale for the machine was UK date style and UK English.
> 3) In the Excel SS, set the column to have a custom date format dd-mmm-yyyy
> [1]
> 4) In the machine Settings, US English semed to be above UK English, so we
> fixed that and he logged out/in.
>
> But: whatever we did, the date field in the merged Word doc always showed the
> date as mm/dd/yy.
>
> Any suggestions for how to make the merged field in the Word doc contain the
> date in the same format as in the Excel SS would be most welcome.
>
>
> [1] Oddly, when we did this, some dates showed as dd-mmm-yyyy in that SS
> column, but some continued to show as dd/mm/yy.

Yup can be a PITA, sometimes you seem to have all the regional settings
correct, but it still gives an unexpected format.

There is a way to explicitly choose the format of merge fields in Word -
very handy for dates but also has lots of other applications like
formatting numbers as currency etc.

So lets say the spreadsheet has a column with the title "Date". If you
tell word to include this in the form letter using the "Insert Merge
Field" button it will drop a token into the document that will look a
bit like:

<<Date>>

(the << and >> are single custom ligature characters)

If while viewing the document you do ALT+F9, that will change the view
of all the merge fields to show you their actual content, and more
importantly, make them editable.

So the <<Date>> will change to something in the form:

{ MERGEFIELD Date }

You can now edit that to include a format. You do this by adding a
formatting marker "\@" after the name of the field, and then the actual
format required.

So to render it as dd/mm/yyyy you would change it to read:

{ MERGEFIELD Date \@ dd/MM/yyyy }

(again the {} characters are not "normal" and you can't just type them -
although you can enter a pair of them using CTRL + F9) [1]

The merge format characters vary in effect depending on how many you use
and the case.

So if we were formatting 05/02/2023

dd/MM/yyyy -> 05/02/2023

d-MM-yy -> 5-02-2023

MMMM d, yyyy -> February 5, 2023

dd MMM yy -> 05 Feb 23

Or you can get posh with :

{ MERGEFIELD Date \@ d \* Ordinal }{ MERGEFIELD Date \@ MMMM }{
MERGEFIELD Date \@ yyyy }

Which gives -> 5th February 2023

[1]

Handy if you want to write your own merge fields with conditional logic.
e.g.

{ IF { MERGEFIELD Title } = "Mr" "Dear Sir," "Dear Madam," }

--
Cheers,

John.

/=================================================================\
| Internode Ltd - http://www.internode.co.uk |
|-----------------------------------------------------------------|
| John Rumm - john(at)internode(dot)co(dot)uk |
\=================================================================/

On 21/02/2023 in message <tt3kqe$18rgt$1@dont-email.me> John Rumm wrote:

>{IF { MERGEFIELD Title } = "Mr" "Dear Sir," "Dear Madam," }

I'm not the OP but that is incredibly useful, thank you, saved in my help
directory :-)

--
Jeff Gaines Dorset UK
If you ever find something you like buy a lifetime supply because they
will stop making it

On 21 Feb 2023 at 23:41:01 GMT, "John Rumm" <see.my.signature@nowhere.null>
wrote:

> On 21/02/2023 21:52, Tim Streater wrote:
>> I watched this chap today have a mailmerge problem. He had a spreadsheet with
>> say 30 rows, one column of which was supposed to contain dates in UK format,
>> such as 21/2/23 for today. When he used the date column to merge into the Word
>> doc, the dates kept coming out in the merged doc as 2/21/23, US style.
>>
>> I made these suggestions:
>>
>> 1) Check the Word doc has UK English set as language.
>> 2) Check that the locale for the machine was UK date style and UK English.
>> 3) In the Excel SS, set the column to have a custom date format dd-mmm-yyyy
>> [1]
>> 4) In the machine Settings, US English semed to be above UK English, so we
>> fixed that and he logged out/in.
>>
>> But: whatever we did, the date field in the merged Word doc always showed the
>> date as mm/dd/yy.
>>
>> Any suggestions for how to make the merged field in the Word doc contain the
>> date in the same format as in the Excel SS would be most welcome.
>>
>>
>> [1] Oddly, when we did this, some dates showed as dd-mmm-yyyy in that SS
>> column, but some continued to show as dd/mm/yy.
>
> Yup can be a PITA, sometimes you seem to have all the regional settings
> correct, but it still gives an unexpected format.
>
> There is a way to explicitly choose the format of merge fields in Word -
> very handy for dates but also has lots of other applications like
> formatting numbers as currency etc.
>
> So lets say the spreadsheet has a column with the title "Date". If you
> tell word to include this in the form letter using the "Insert Merge
> Field" button it will drop a token into the document that will look a
> bit like:
>
> <<Date>>
>
> (the << and >> are single custom ligature characters)
>
> If while viewing the document you do ALT+F9, that will change the view
> of all the merge fields to show you their actual content, and more
> importantly, make them editable.
>
> So the <<Date>> will change to something in the form:
>
> { MERGEFIELD Date }
>
> You can now edit that to include a format. You do this by adding a
> formatting marker "\@" after the name of the field, and then the actual
> format required.
>
> So to render it as dd/mm/yyyy you would change it to read:
>
> { MERGEFIELD Date \@ dd/MM/yyyy }
>
> (again the {} characters are not "normal" and you can't just type them -
> although you can enter a pair of them using CTRL + F9) [1]
>
>
> The merge format characters vary in effect depending on how many you use
> and the case.
>
> So if we were formatting 05/02/2023
>
> dd/MM/yyyy -> 05/02/2023
>
> d-MM-yy -> 5-02-2023
>
> MMMM d, yyyy -> February 5, 2023
>
> dd MMM yy -> 05 Feb 23
>
> Or you can get posh with :
>
> { MERGEFIELD Date \@ d \* Ordinal }{ MERGEFIELD Date \@ MMMM }{
> MERGEFIELD Date \@ yyyy }
>
> Which gives -> 5th February 2023
>
>
>
> [1]
>
> Handy if you want to write your own merge fields with conditional logic.
> e.g.
>
> { IF { MERGEFIELD Title } = "Mr" "Dear Sir," "Dear Madam," }

Well, dash my wig!

Thanks John, I will transmit that to the chap having the issue. I tried this
also with Office 2016 for macOS, and somewhat to my surprise switching the
view of the field codes works with ALT-F9 there too. Or by right-mouse on the
field code and select "Toggle field codes" (whether it does them all or just
that one, I didn't test).

--
Lady Astor: "If you were my husband I'd give you poison."
Churchill: "If you were my wife, I'd drink it."

On Wednesday, 22 February 2023 at 08:35:06 UTC, Jeff Gaines wrote:
> On 21/02/2023 in message <tt3kqe$18rgt$1...@dont-email.me> John Rumm wrote:
> >{IF { MERGEFIELD Title } = "Mr" "Dear Sir," "Dear Madam," }
> I'm not the OP but that is incredibly useful, thank you, saved in my help
> directory :-)

I take it you don't know many Doctors? :)

Owain

Tim Streater wrote:

> He had a spreadsheet with say 30 rows, one column of which was
> supposed to contain dates in UK format

What was the "format" type of the date column, hopefully "date" rather
than "text" or "number/general"?

On 22 Feb 2023 10:44:47 GMT

>
> > On 21/02/2023 21:52, Tim Streater wrote:
> >> I watched this chap today have a mailmerge problem. He had a
> >> spreadsheet with say 30 rows, one column of which was supposed to
> >> contain dates in UK format, such as 21/2/23 for today. When he
> >> used the date column to merge into the Word doc, the dates kept
> >> coming out in the merged doc as 2/21/23, US style.
> >>

I had this problem years ago, but with Access and Excel. What was odd
was that only a few of the dates came out wrong, the rest were right.
The penny eventually dropped: the correct dates were where the day
number was greater than twelve.

Here also, both Access and Excel had correct regional/cultural
settings, but the transfer process between them didn't respect either.
It treated the dates as US, *except* when the month number would be
greater than 12, when it realised that would be wrong and used the UK
format. What idiot programmer did that? If one is wrong, they're all
wrong.

I can't remember now how I fixed it, but there are several possible
workarounds. You just have to know that you need to use one of them.
These days I tend to use ISO format (yyyy-mm-dd) for dates internally,
with the added advantage that an alphabetic sort gets them in the right
order.

--
Joe

On 22/02/2023 10:45, Owain Lastname wrote:
> On Wednesday, 22 February 2023 at 08:35:06 UTC, Jeff Gaines wrote:
>> On 21/02/2023 in message <tt3kqe$18rgt$1...@dont-email.me> John Rumm wrote:

>>> {IF { MERGEFIELD Title } = "Mr" "Dear Sir," "Dear Madam," }

>> I'm not the OP but that is incredibly useful, thank you, saved in my help
>> directory :-)
>
> I take it you don't know many Doctors? :)

You just need an illegible handwriting font for them! :-)

The IF THEN ELSE logic gets a bit more cludgy in layout if you need
nested clauses:

{ IF { MERGEFIELD Title } = "Dr" "Dear Doctor," "{ IF { MERGFIELD Title
} = "Mr" "Dear Sir," "Dear Madam," } }

You can carry on sticking extra IF constructions into the third
parameter of the preceding construction to create a nested chain:

If then
Something
else
if something else
something else
else
if yet something
yet somethiung
endif
endif
endif

Alas now switch or case statement! (if it gets complex it is probably
better to do some of the work in the data source first)

--
Cheers,

John.

/=================================================================\
| Internode Ltd - http://www.internode.co.uk |
|-----------------------------------------------------------------|
| John Rumm - john(at)internode(dot)co(dot)uk |
\=================================================================/

On 22/02/2023 10:44, Tim Streater wrote:
> On 21 Feb 2023 at 23:41:01 GMT, "John Rumm" <see.my.signature@nowhere.null>
> wrote:
>
>> On 21/02/2023 21:52, Tim Streater wrote:
>>> I watched this chap today have a mailmerge problem. He had a spreadsheet with
>>> say 30 rows, one column of which was supposed to contain dates in UK format,
>>> such as 21/2/23 for today. When he used the date column to merge into the Word
>>> doc, the dates kept coming out in the merged doc as 2/21/23, US style.

> Well, dash my wig!
>
> Thanks John, I will transmit that to the chap having the issue. I tried this
> also with Office 2016 for macOS, and somewhat to my surprise switching the
> view of the field codes works with ALT-F9 there too. Or by right-mouse on the
> field code and select "Toggle field codes" (whether it does them all or just
> that one, I didn't test).

Some Macs need Fn ALT-F9, but yup the process should be the same on both.

--
Cheers,

John.

/=================================================================\
| Internode Ltd - http://www.internode.co.uk |
|-----------------------------------------------------------------|
| John Rumm - john(at)internode(dot)co(dot)uk |
\=================================================================/

On 22/02/2023 11:10, Joe wrote:
> On 22 Feb 2023 10:44:47 GMT
>
>>
>>> On 21/02/2023 21:52, Tim Streater wrote:
>>>> I watched this chap today have a mailmerge problem. He had a
>>>> spreadsheet with say 30 rows, one column of which was supposed to
>>>> contain dates in UK format, such as 21/2/23 for today. When he
>>>> used the date column to merge into the Word doc, the dates kept
>>>> coming out in the merged doc as 2/21/23, US style.
>>>>
>
> I had this problem years ago, but with Access and Excel. What was odd
> was that only a few of the dates came out wrong, the rest were right.
> The penny eventually dropped: the correct dates were where the day
> number was greater than twelve.
>
> Here also, both Access and Excel had correct regional/cultural
> settings, but the transfer process between them didn't respect either.
> It treated the dates as US, *except* when the month number would be
> greater than 12, when it realised that would be wrong and used the UK
> format. What idiot programmer did that? If one is wrong, they're all
> wrong.
>
> I can't remember now how I fixed it, but there are several possible
> workarounds. You just have to know that you need to use one of them.
> These days I tend to use ISO format (yyyy-mm-dd) for dates internally,
> with the added advantage that an alphabetic sort gets them in the right
> order.

One thing to check is that you have explicitly formatted the column in
excel etc as a date field. Sometimes it will infer that it should treat
a number as a date, but it not actually be explicitly set to that.

--
Cheers,

John.

/=================================================================\
| Internode Ltd - http://www.internode.co.uk |
|-----------------------------------------------------------------|
| John Rumm - john(at)internode(dot)co(dot)uk |
\=================================================================/

On 22/02/2023 in message
<16a8df10-a79c-434c-934c-1fb29c2a3a3dn@googlegroups.com> Owain Lastname
wrote:

>On Wednesday, 22 February 2023 at 08:35:06 UTC, Jeff Gaines wrote:
>>On 21/02/2023 in message <tt3kqe$18rgt$1...@dont-email.me> John Rumm
>>wrote:
>>>{IF { MERGEFIELD Title } = "Mr" "Dear Sir," "Dear Madam," }
>>I'm not the OP but that is incredibly useful, thank you, saved in my help
>>directory :-)
>
>I take it you don't know many Doctors? :)
>
>Owain

I was lucky enough to have an appointment with one once, about 3 years ago
from memory!

--
Jeff Gaines Dorset UK
Indecision is the key to flexibility

On 22 Feb 2023 at 10:59:25 GMT, "Andy Burns" <usenet@andyburns.uk> wrote:

> Tim Streater wrote:
>
>> He had a spreadsheet with say 30 rows, one column of which was
>> supposed to contain dates in UK format
>
> What was the "format" type of the date column, hopefully "date" rather
> than "text" or "number/general"?

<font color="#000000">We applied "Custom format" and a format of
dd-mmm-yyyy.</font>

--
"Once you adopt the unix paradigm, the variants cease to be a problem - you bitch, of course, but that's because bitching is fun, unlike M$ OS's, where bitching is required to keep your head from exploding." - S Stremler in afc

On 22 Feb 2023 at 11:10:14 GMT, "Joe" <joe@jretrading.com> wrote:

> On 22 Feb 2023 10:44:47 GMT
>
>>
>>> On 21/02/2023 21:52, Tim Streater wrote:
>>>> I watched this chap today have a mailmerge problem. He had a
>>>> spreadsheet with say 30 rows, one column of which was supposed to
>>>> contain dates in UK format, such as 21/2/23 for today. When he
>>>> used the date column to merge into the Word doc, the dates kept
>>>> coming out in the merged doc as 2/21/23, US style.
>>>>
>
> I had this problem years ago, but with Access and Excel. What was odd
> was that only a few of the dates came out wrong, the rest were right.
> The penny eventually dropped: the correct dates were where the day
> number was greater than twelve.
>
> Here also, both Access and Excel had correct regional/cultural
> settings, but the transfer process between them didn't respect either.
> It treated the dates as US, *except* when the month number would be
> greater than 12, when it realised that would be wrong and used the UK
> format. What idiot programmer did that? If one is wrong, they're all
> wrong.
>
> I can't remember now how I fixed it, but there are several possible
> workarounds. You just have to know that you need to use one of them.
> These days I tend to use ISO format (yyyy-mm-dd) for dates internally,
> with the added advantage that an alphabetic sort gets them in the right
> order.

I store all dates/times as seconds since the epoch, as this is the data
storage layer. Those are then converted for presentation to the user, with the
format chosen by the user.

--
Tim

I suspect that dates put in before the change to the correct format will
always be wrong but those after will be correct. This is or was in a very
old version, so I'm surprised if its still the case.
Brian

--

--:
This newsgroup posting comes to you directly from...
The Sofa of Brian Gaff...
briang1@blueyonder.co.uk
Blind user, so no pictures please
Note this Signature is meaningless.!
"Roger Mills" <mills37.fslife@gmail.com> wrote in message
news:k5l240F4uafU1@mid.individual.net...
> On 21/02/2023 21:52, Tim Streater wrote:
>> I watched this chap today have a mailmerge problem. He had a spreadsheet
>> with
>> say 30 rows, one column of which was supposed to contain dates in UK
>> format,
>> such as 21/2/23 for today. When he used the date column to merge into the
>> Word
>> doc, the dates kept coming out in the merged doc as 2/21/23, US style.
>>
>> I made these suggestions:
>>
>> 1) Check the Word doc has UK English set as language.
>> 2) Check that the locale for the machine was UK date style and UK
>> English.
>> 3) In the Excel SS, set the column to have a custom date format
>> dd-mmm-yyyy
>> [1]
>> 4) In the machine Settings, US English semed to be above UK English, so
>> we
>> fixed that and he logged out/in.
>>
>> But: whatever we did, the date field in the merged Word doc always showed
>> the
>> date as mm/dd/yy.
>>
>> Any suggestions for how to make the merged field in the Word doc contain
>> the
>> date in the same format as in the Excel SS would be most welcome.
>>
>>
>> [1] Oddly, when we did this, some dates showed as dd-mmm-yyyy in that SS
>> column, but some continued to show as dd/mm/yy.
>
> Dunno, but a possible workaround may be to have three date fields instead
> of one. You can use formulae in Excel to create 3 columns - one for day,
> one for month and one for year. You can then use the mail-merge to control
> how those 3 fields appear in the Word document.
> Or, if you only want one field, create a text string in Excel with the
> date in your chosen format, and use that in the mail merge.
> --
> Cheers,
> Roger
>

On 22 Feb 2023 at 15:48:38 GMT, ""Brian Gaff"" <brian1gaff@gmail.com> wrote:

> I suspect that dates put in before the change to the correct format will
> always be wrong but those after will be correct. This is or was in a very
> old version, so I'm surprised if its still the case.

What is an old version? Chummy was using Office 365 under Win-11.

I on the other hand use Office 2016 under macOS, still perfectly adequate for
all that its Help insists that this version has been retired. But since the
app continues to work it can't have been retired.

--
"Once you adopt the unix paradigm, the variants cease to be a problem - you bitch, of course, but that's because bitching is fun, unlike M$ OS's, where bitching is required to keep your head from exploding." - S Stremler in afc

On 22/02/2023 17:32, Tim Streater wrote:
> On 22 Feb 2023 at 15:48:38 GMT, ""Brian Gaff"" <brian1gaff@gmail.com> wrote:
>
>> I suspect that dates put in before the change to the correct format will
>> always be wrong but those after will be correct. This is or was in a very
>> old version, so I'm surprised if its still the case.
>
> What is an old version? Chummy was using Office 365 under Win-11.
>
> I on the other hand use Office 2016 under macOS, still perfectly adequate for
> all that its Help insists that this version has been retired. But since the
> app continues to work it can't have been retired.

2016 is still a supported version. 2010 is now out of support, and 2013
is/will be soon.

--
Cheers,

John.

/=================================================================\
| Internode Ltd - http://www.internode.co.uk |
|-----------------------------------------------------------------|
| John Rumm - john(at)internode(dot)co(dot)uk |
\=================================================================/

Tim Streater wrote:

> We applied "Custom format" and a format of dd-mmm-yyyy.

If it doesn't display consistently within excel, suggests not imported
correctly, unlikely to merge properly until you fix it inside excel, did
it start life as a .csv?

In article <tt5kio$1ipuc$2@dont-email.me>, John Rumm
<see.my.signature@nowhere.null> wrote:
> On 22/02/2023 17:32, Tim Streater wrote:
> > On 22 Feb 2023 at 15:48:38 GMT, ""Brian Gaff"" <brian1gaff@gmail.com>
> > wrote:
> >
> >> I suspect that dates put in before the change to the correct format
> >> will always be wrong but those after will be correct. This is or was
> >> in a very old version, so I'm surprised if its still the case.
> >
> > What is an old version? Chummy was using Office 365 under Win-11.
> >
> > I on the other hand use Office 2016 under macOS, still perfectly
> > adequate for all that its Help insists that this version has been
> > retired. But since the app continues to work it can't have been retired.

> 2016 is still a supported version. 2010 is now out of support, and 2013
> is/will be soon.

Mine is 2007!

--
from KT24 in Surrey, England - sent from my RISC OS 4té
"I'd rather die of exhaustion than die of boredom" Thomas Carlyle

On 22 Feb 2023 at 17:49:12 GMT, "John Rumm" <see.my.signature@nowhere.null>
wrote:

> On 22/02/2023 17:32, Tim Streater wrote:
>> On 22 Feb 2023 at 15:48:38 GMT, ""Brian Gaff"" <brian1gaff@gmail.com> wrote:
>>
>>> I suspect that dates put in before the change to the correct format will
>>> always be wrong but those after will be correct. This is or was in a very
>>> old version, so I'm surprised if its still the case.
>>
>> What is an old version? Chummy was using Office 365 under Win-11.
>>
>> I on the other hand use Office 2016 under macOS, still perfectly adequate for
>> all that its Help insists that this version has been retired. But since the
>> app continues to work it can't have been retired.
>
> 2016 is still a supported version.

Not according to support.microsoft.com, who say:

Support for Office 2016 for Mac ended on October 13, 2020. Rest assured that
all your Office 2016 apps ...

> 2010 is now out of support, and 2013 is/will be soon.

I only got it because Office 2008 is only 32-bit and now I've moved to
Catalina, 32-bit apps don't run.

--
If socialism helps the poor, why are the poor in socialist countries so much poorer than the poor in capitalist countries?

Mark

On Wed, 22 Feb 2023 21:45:12 +1100, Owain Lastname
<spuorgelgoog@gowanhill.com> wrote:

> On Wednesday, 22 February 2023 at 08:35:06 UTC, Jeff Gaines wrote:
>> On 21/02/2023 in message <tt3kqe$18rgt$1...@dont-email.me> John Rumm
>> wrote:
>> >{IF { MERGEFIELD Title } = "Mr" "Dear Sir," "Dear Madam," }
>> I'm not the OP but that is incredibly useful, thank you, saved in my
>> help
>> directory :-)
>
> I take it you don't know many Doctors? :)

I know lots of them but never snail mail them and always use their first
name with no title.

On 22/02/2023 18:09, charles wrote:
> In article <tt5kio$1ipuc$2@dont-email.me>, John Rumm
> <see.my.signature@nowhere.null> wrote:
>> On 22/02/2023 17:32, Tim Streater wrote:
>>> On 22 Feb 2023 at 15:48:38 GMT, ""Brian Gaff"" <brian1gaff@gmail.com>
>>> wrote:
>>>
>>>> I suspect that dates put in before the change to the correct format
>>>> will always be wrong but those after will be correct. This is or was
>>>> in a very old version, so I'm surprised if its still the case.
>>>
>>> What is an old version? Chummy was using Office 365 under Win-11.
>>>
>>> I on the other hand use Office 2016 under macOS, still perfectly
>>> adequate for all that its Help insists that this version has been
>>> retired. But since the app continues to work it can't have been retired.
>
>> 2016 is still a supported version. 2010 is now out of support, and 2013
>> is/will be soon.
>
> Mine is 2007!

The last one with proper menus! :-)

--
Cheers,

John.

/=================================================================\
| Internode Ltd - http://www.internode.co.uk |
|-----------------------------------------------------------------|
| John Rumm - john(at)internode(dot)co(dot)uk |
\=================================================================/

On 22/02/2023 18:44, Tim Streater wrote:
> On 22 Feb 2023 at 17:49:12 GMT, "John Rumm" <see.my.signature@nowhere.null>
> wrote:
>
>> On 22/02/2023 17:32, Tim Streater wrote:
>>> On 22 Feb 2023 at 15:48:38 GMT, ""Brian Gaff"" <brian1gaff@gmail.com> wrote:
>>>
>>>> I suspect that dates put in before the change to the correct format will
>>>> always be wrong but those after will be correct. This is or was in a very
>>>> old version, so I'm surprised if its still the case.
>>>
>>> What is an old version? Chummy was using Office 365 under Win-11.
>>>
>>> I on the other hand use Office 2016 under macOS, still perfectly adequate for
>>> all that its Help insists that this version has been retired. But since the
>>> app continues to work it can't have been retired.
>>
>> 2016 is still a supported version.
>
> Not according to support.microsoft.com, who say:
>
> Support for Office 2016 for Mac ended on October 13, 2020. Rest assured that
> all your Office 2016 apps ...

My bad - I was taking Windows. Mac versions seem to be a bit out of sync
with windows ones...

>> 2010 is now out of support, and 2013 is/will be soon.
>
> I only got it because Office 2008 is only 32-bit and now I've moved to
> Catalina, 32-bit apps don't run.

VirtuaBox may sort it... (tis how I run a Mac on my machine)

--
Cheers,

John.

/=================================================================\
| Internode Ltd - http://www.internode.co.uk |
|-----------------------------------------------------------------|
| John Rumm - john(at)internode(dot)co(dot)uk |
\=================================================================/

On 22 Feb 2023 at 18:05:55 GMT, "Andy Burns" <usenet@andyburns.uk> wrote:

> Tim Streater wrote:
>
>> We applied "Custom format" and a format of dd-mmm-yyyy.
>
> If it doesn't display consistently within excel, suggests not imported
> correctly, unlikely to merge properly until you fix it inside excel, did
> it start life as a .csv?

No, data entered by hand I suspect.

--
The truth of the matter is that we Scots have always been more divided amongst ourselves than pitted against the English. Scottish history before the Union of Parliaments is a gloomy, violent tale of murders, feuds, and tribal revenge. Only after the Act of Union did Highlanders and Lowlanders, Picts and Celts, begin to recognise one another as fellow citizens.

Tam Dalyell

On Thu, 23 Feb 2023 05:09:59 +1100, charles <charles@candehope.me.uk>
wrote:

> In article <tt5kio$1ipuc$2@dont-email.me>, John Rumm
> <see.my.signature@nowhere.null> wrote:
>> On 22/02/2023 17:32, Tim Streater wrote:
>> > On 22 Feb 2023 at 15:48:38 GMT, ""Brian Gaff"" <brian1gaff@gmail.com>
>> > wrote:
>> >
>> >> I suspect that dates put in before the change to the correct format
>> >> will always be wrong but those after will be correct. This is or was
>> >> in a very old version, so I'm surprised if its still the case.
>> >
>> > What is an old version? Chummy was using Office 365 under Win-11.
>> >
>> > I on the other hand use Office 2016 under macOS, still perfectly
>> > adequate for all that its Help insists that this version has been
>> > retired. But since the app continues to work it can't have been
>> retired.
>
>> 2016 is still a supported version. 2010 is now out of support, and 2013
>> is/will be soon.
>
> Mine is 2007!

You dinosaur.