• WSPaul Lautman

    WSPaul Lautman

    @wspaul-lautman

    Viewing 15 replies - 136 through 150 (of 212 total)
    Author
    Replies
    • in reply to: Fully underlined heading (2002 SP3) #886053

      Thanks Hans, I’ll try that out soon and report back.

    • in reply to: Fully underlined heading (2002 SP3) #886016

      My document currently has only 1 line in it. The problem occurs regardless of what document I am in. If I try to retype the preface text in Modify Style->Numbering then after typing a few characters word just hangs. It does not go not responding, but it does nothing else. I can adjust the format of the particular heading and then “Update to match” and then all is fine.

    • in reply to: Fully underlined heading (2002 SP3) #886017

      My document currently has only 1 line in it. The problem occurs regardless of what document I am in. If I try to retype the preface text in Modify Style->Numbering then after typing a few characters word just hangs. It does not go not responding, but it does nothing else. I can adjust the format of the particular heading and then “Update to match” and then all is fine.

    • in reply to: Fully underlined heading (2002 SP3) #885899

      Thanks Hans, I knew I’d managed to get it looking almost good at one point, I must have chosed outline numbering then.

      What is the difference between Standard and Outline numbering? I thought it was just that there was more than one level in an outline list.

      Sure like to know why I get word hanging everytime I try to modify the number prefix directly in the style. The only think I can do after that is bring up the task manager and end the task.

      As I say, changing the prefix “in situ” and then updating a style to match the selection works fine.

    • in reply to: Fully underlined heading (2002 SP3) #885874

      Also, I still seem to have a gap, even after following your instructions.

      I have attached the file

    • in reply to: Fully underlined heading (2002 SP3) #885875

      Also, I still seem to have a gap, even after following your instructions.

      I have attached the file

    • in reply to: Fully underlined heading (2002 SP3) #885872

      I have had trouble updating the styles with “Session”. Whenever I do, as I start typing session, I get a message telling me that the document is too large and then word just hangs.

      The only way that I have managed to add the Session is to format the text and then choose “Update to match selection”

    • in reply to: Fully underlined heading (2002 SP3) #885873

      I have had trouble updating the styles with “Session”. Whenever I do, as I start typing session, I get a message telling me that the document is too large and then word just hangs.

      The only way that I have managed to add the Session is to format the text and then choose “Update to match selection”

    • in reply to: .value = .value screwing date format (2002 SP2) #884659

      Cheers Rory,
      the description on the problem at the link that you sent was not exactly what I was seeing, but it sure cured the problem.

    • in reply to: .value = .value screwing date format (2002 SP2) #884660

      Cheers Rory,
      the description on the problem at the link that you sent was not exactly what I was seeing, but it sure cured the problem.

    • in reply to: .value = .value screwing date format (2002 SP2) #884402

      That isn’t listed in my Region Settings. Mine is set to dd/MM/yyyy

      As I just added to my original post, I only see the problem if more than one cell is selected when I run the macro.

      I have attached pd2.xls which shows the results of running propagate_data1 on a single cell (C3) and on multiple cells (C10 and C11 selected.

      It also has a picture of my regional settings dialog.

      I tried setting my date settings to dd-MM-yyyy which seems to be the nearest that I can get to your dd-mm-yyyy one, but I still see the problem if more than one cell is selected.

    • in reply to: .value = .value screwing date format (2002 SP2) #884377

      Well, this had me really confused.

      I hope someone can help with a good fix.

      I have a macro called Propagate_Data. It allows me to copy down summarised headings against all rows.

      The original version was:
      Sub propagate_data()
      With Selection
      .SpecialCells(xlCellTypeBlanks).FormulaR1C1 = “=R[-1]C”
      .Copy
      .PasteSpecial Paste:=xlPasteValues, Operation:=xlNone, SkipBlanks _
      :=False, Transpose:=False
      End With
      Application.CutCopyMode = False
      End Sub

      But I recently started using a newer version:
      Sub propagate_data()
      With Selection
      .SpecialCells(xlCellTypeBlanks).FormulaR1C1 = “=R[-1]C”
      .Value = .Value
      End With
      End Sub

      Everything was going swimmingly, until I I just tried to use the new version against a list of dates.

      The dates in UK format were 01/05/2004, 01/06/2004, 01/07/2004, 01/08/2004 and were formatted on the sheet as May-04, Jun-04, …

      Now, when I ran the latter version of my propagate_data macro, all the dates were displayed as Jan-04.

      When I examined the actual contents of the cells I am seeing 05/01/2004, 06/01/2004, …

      The former version of propagate_data works fine, but the latter version, using .value = .value seems to assume that it is either reading from or writing to the US data format.

      Now, whilst I can in this case simply change back to using the older version of propagate_data, there are other macros that I (and I’m sure others) have that use .value = .value.

      So, any ideas as to how to persuade Excel to consistently use the correct date format?

      I have attached a sample file with 2 macros to compare the results.

      Just select one of the 2 columns and run one of the macros, then select the other column and run the second one.

      I suspect that only non-US folks will be able to see the problem descrivbed above.

      Any assistance would be appreciated.

      Futher information found: This only happens if there is more than one cell selected when “.value = .value” is run. If only 1 cell is selected, then the date format is converted correctly, if more than one is selected, then the error appears.

    • in reply to: .value = .value screwing date format (2002 SP2) #884378

      Well, this had me really confused.

      I hope someone can help with a good fix.

      I have a macro called Propagate_Data. It allows me to copy down summarised headings against all rows.

      The original version was:
      Sub propagate_data()
      With Selection
      .SpecialCells(xlCellTypeBlanks).FormulaR1C1 = “=R[-1]C”
      .Copy
      .PasteSpecial Paste:=xlPasteValues, Operation:=xlNone, SkipBlanks _
      :=False, Transpose:=False
      End With
      Application.CutCopyMode = False
      End Sub

      But I recently started using a newer version:
      Sub propagate_data()
      With Selection
      .SpecialCells(xlCellTypeBlanks).FormulaR1C1 = “=R[-1]C”
      .Value = .Value
      End With
      End Sub

      Everything was going swimmingly, until I I just tried to use the new version against a list of dates.

      The dates in UK format were 01/05/2004, 01/06/2004, 01/07/2004, 01/08/2004 and were formatted on the sheet as May-04, Jun-04, …

      Now, when I ran the latter version of my propagate_data macro, all the dates were displayed as Jan-04.

      When I examined the actual contents of the cells I am seeing 05/01/2004, 06/01/2004, …

      The former version of propagate_data works fine, but the latter version, using .value = .value seems to assume that it is either reading from or writing to the US data format.

      Now, whilst I can in this case simply change back to using the older version of propagate_data, there are other macros that I (and I’m sure others) have that use .value = .value.

      So, any ideas as to how to persuade Excel to consistently use the correct date format?

      I have attached a sample file with 2 macros to compare the results.

      Just select one of the 2 columns and run one of the macros, then select the other column and run the second one.

      I suspect that only non-US folks will be able to see the problem descrivbed above.

      Any assistance would be appreciated.

      Futher information found: This only happens if there is more than one cell selected when “.value = .value” is run. If only 1 cell is selected, then the date format is converted correctly, if more than one is selected, then the error appears.

    • in reply to: Line above text (2002 SP2) #882416

      Thanks Hans and Rudi.

      And there is of course the {eq …} field trick.

      I just thought that I recalled an easy way to select whether the line went the whole width or just the width of the actual characters in the heading paragraph.

      It was obviously a false memory.

      Thanks for helping.

    • in reply to: Line above text (2002 SP2) #882417

      Thanks Hans and Rudi.

      And there is of course the {eq …} field trick.

      I just thought that I recalled an easy way to select whether the line went the whole width or just the width of the actual characters in the heading paragraph.

      It was obviously a false memory.

      Thanks for helping.

    Viewing 15 replies - 136 through 150 (of 212 total)