What I meant was, your macro could begin by creating a new field, then selecting it and deleting it - and then running the important part of the macro that has the formatting in it. I don't honestly know if this would work to trigger the OOo code Patrick's workaround is working around, but it's worth a try, and wouldn't slow the macro down much, I think.
If it works, then you just need to run the macro, which will work fine in a new or an existing doc, and you wouldn't have to create-and-delete the extra field yourself first using keyboard/menus, and she'll be apples .
What I meant was, your macro could begin by creating a new field, then selecting it and deleting it - and then running the important part of the macro that has the formatting in it. I don't honestly know if this would work to trigger the OOo code Patrick's workaround is working around, but it's worth a try, and wouldn't slow the macro down much, I think.
Unfortunately, that will not work as the OpenOffice.org bug will occur in every date or time field that you insert from a macro until after you have manually inserted a date or time field.
Essentially, the bug is that some necessary document state setting has to be enabled for the macro to work and, so far, the only action that switches that macro on is manually inserting a date or time field.
All times are GMT - 7 Hours Goto page Previous1, 2
Page 2 of 2
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum You cannot attach files in this forum You cannot download files in this forum
.
