Replies

[indent]

---

The new styles should be listed in Available styles. Are they listed when you select All styles in the Styles and Formatting task pane?

---

[/indent]
That is where I expected to find them, but no they are not there.

However I have just discovered that if I go to Tools->Templates and Add-ins and check the box Automatically update document styles, then the new styles appear.

Wow thanks Hans. The MsgBox is as useful as it needs to get.

One other thing, which I know I have asked and had resolved somewhere before.

How does one remember where the cursor started and return to that position at the end of running the macro.

Naively I have tried

Set orig = Selection
.
.
.
.
orig.Select

But I remember that there needs to be a bit more to actually get it to function properly.

TIA

As requested

My problem is how to go fetch all the values to add up.

The Date Calculations stuff doesn’t seem to help in this.

Adding the numbers up in VBA isn’t a problem, it is how I get all the numbers out of the text in the first place.

Any help appreciated.

I don’t have the Works CD, but I’m sure I can do without the functionality (not that I have any idea what it actually does!)

I removed it and Word is “cooking with gas” once again.

Thanks for your help Tony.

OK, here’s what I found.

Running “winword /a” works great.

I deleted all the “*.tmp;~*.do?;~*.wbk” that I possibly could, no improvement 🙁

I had already renamed normal.dot but removed it from the templates directory as instructed, no improvement 🙁

I used the SUPPORT.DOT template to delete the data key, rename Word Startup Folder Addins (none to rename), delete the COM-Addins registry key, delete the Options registry key; no improvement 🙁

The only addins that I can find are revealed by the code snippit and they are “MicrosoftWorks WordAddIN – MicrosoftWorks.WordAddIN.6”

But none of the instructions tell me what to do to fix the problem that seems to be being caused by these addins (assuming that it is indeed these that are the problem)???

What next?

Thanks, I’ll try that tonight and post an update.

In the meanwhile I’m using OpenOffice Write.

[indent]

---

I am confused though as to why the assignment to a boolean variable does not force the values to be true booleans.

---

[/indent]

Yes, but stranger than that is, if you look at my post 480946, that it DOES work, but only if I do not try to use Not in the same statement.

Well coding the Cbool() changes things.

ir = CBool(oia.waitforinputready(10000))
nir = Not ir

Ends up with ir = True and nir = False

But

ir = Not CBool(oia.waitforinputready(10000))
nir = Not ir

Still has ir = True and nir = True

I didn’t Dim it in the attached workbook, but if you look at the picture in the first append, I did have them Dimmed as Boolean and it was still exhibiting the behaviour.

Also a Debug.Print of oia.waitforinputready(n) returns True or False.

Bottom line is, is there some way that I can code this to make a working True/False value?

I didn’t think you would have, that was why I inserted the 3 pictures into the workbook.

A very strange situation!

Edited by StuartR to reduce size of graphic

I am seeing some very strange behaviour when writing a programmed operator using VBA in Excel. I wonder if anyone can explain it.

The programmed operator is using OLE to interact with an IBM Personal Communications 3270 emulator.

One ofthe methods available is WaitForInputReady for which the documentation says:

Method: Boolean WaitForInputReady

The WaitForInputReady method waits until the OIA of the connection associated with autECLOIA object indicates that the connection is able to accept keyboard input

Input Parameters:

Still there after a reboot.
The attached worksheet contains a small piece of test code. Obviously you can’t run it unless you have IBM Personal Communications on your PC.

Sheets 1 to 3 show results of 3 tests:

Sheet 1:
With a timeout of 1000 milliseconds, oia.waitforinputready() returns False.
You can see that ir = False and Not ir = True
This is as expected.

Sheet 2:
With a timeout of 10000 milliseconds, oia.waitforinputready() returns True.
You can see that ir = True and Not ir = True
This is NOT as expected

Sheet 3:
Setting ir to True explicitly (even though with a timeout of 10000 milliseconds it would already have been True) gives us:
ir = True and Not ir = False
Once again as expected.

Thanks Rudi, maybe the blank colum header was the trick. It still shouldn’t be this difficult!

Any normal user would expect at anto filter of “does not equal” 0123 (which appears in the drop down list, to work, rather than having to use “does not contain”, which of course will not do exactly the same thing.

Thanks to all who helped reach this solution.

So it seems that Excel triumphs again. Why can’t it just leave one’s data alone!