Replies

For what it’s worth, not only did the Adobe add-in (PDFMaker) cause me much grief in the past, but the Documentum add-in was also notorious for causing the same problem on my machine. In fact, while Adobe caused that problem for me on past configurations/installations, the Documentum one was the most recent culprit.

If you’d like to try and investigate what may have happened, I’d suggest ruling out VBA code hijacking your commands by selecting Tools: Macro>Macros, then select Word Commands from the Macros in… drop-down, and, from the list of available macros, select either FileSave or FileSaveAs and see if it behaves appropriately. If it does, then there might well be code lurking in either the document or its attached template that hijacks the command. (An alternative to this could be launching the VBA editor [Alt-F11], then, if necessary, selecting View: Immediate Window if it’s not already open, and then typing the command ActiveDocument.Save in the Immediate window and hitting ENTER.)

Another possiblity is that the file IS being saved, and that the Close event is triggering some other code that registers (correctly or not) a subseqent but irrelevant change in the file. I wouldn’t be surprised if conflicts in or between add-ins can cause this, as I have seen many compatibility issues between commercially purchased add-ins (Adobe Acrobat, Reference Manager, SnagIt, etc.) in my years of working with Word.

OK, what I found, and what I’m going with, is that a Combo-box works just as I’d expect. I’ll just set the “Limit to List” property to “Yes”, and it will give me the functionality I expect (i.e. no weird highlighting, no having to click in a field before using its pick-list.)

I guess I just can’t impose my will on Microsoft Access.

Yep. And that’s what adds to my confusion. I’m attaching a screen cap that shows both the Form (continuous) and the data property of the first drop-down.

I don’t know if you have this luxury, but one approach that comes to mind is to “hijack” the FileSave command.

The code below will display the Save As… dialog box. If the user clicks “Cancel,” it displays a Message Box; otherwise, it saves the file.

Sub FileSave()
Dim mySaveDialog As Dialog, myAnswer As Integer
Set mySaveDialog = Dialogs(wdDialogFileSaveAs)
myAnswer = mySaveDialog.Show
If myAnswer = 0 Then MsgBox “The file was not saved.”, vbInformation + vbOKOnly, “FileSaveAs Test”
End Sub

Note that, because this sub is named FileSave, it forces the Save As… dialog box to appear every time the user clicks the Save button or chooses File: Save (which seemed to be in keeping with your needs, since that’s the only time one would have the option of clicking on a Cancel button.) I guess one could name it FileSaveAs, in which case it would only appear when the user selected File: Save As…, but it wouldn’t run when the user is saving a file for the very first time, at least not without customizing the toolbars and menus.

Thanks, Hans, as always. I was wondering if I should just resort to the FileSystemObject, if for no other reason than it’s so much more robust and flexible. With respect to the latency: frequently, connecting to a drive for the first time (i.e. clicking on it in Explorer) often takes a couple of seconds here. I was wondering if that time is minimized on subsequent queries (directory calls) because it’s cached or because it becomes (in VB-speak) the “current drive”. I will need to check for the existence of many folders (ostensibly using FolderExists), thus my concern about how to make a share the current drive.

Brilliant! And way better than my (fleeting) idea of opening the Payroll sheet and immediately closing it (after the data was updated). I’m sure there’d be a quick-fingered user ready with a lightning-fast CTRL+Break at the ready…

I’ve been using the “p” prefix to specify the page for many, many years, and I, too, still use the “p” simply because that’s how it was documented in Word’s help file.

FWIW: We prepare documents for submission to regulatory agencies, and regularly work with mutant-documents laden with section breaks, tables, and hidden text, but almost invariably paginated 1 through n. Many times, users have problems printing specific pages from these documents, sometimes even an otherwise simple page range. But, what I have found (and thus practice to this day) is that I never have a problem printing specific pages or page-ranges as long as I use the “pnsn” method of specifying pages, whether or not page re-numbering is used throughout the document.

And, like Hans, learning that the “p” isn’t actually required is very cool and will be useful in my work. Thanks for that!

In my experience, entering something like p3s1-p6s1, p3s2-p6s2, p3s4-p6s4, while verbose, is arguably the best and most efficient way to ensure you’re printing the right pages from the right sections.

Thank you both John and Jefferson. I am now using the Folders collection to great success; I was unsure what that collection was a member of, nor whether I could use it rather than the GetDefaultFolder approach. (I know next to nothing about the Outlook object model.)

John, thanks, but I actually wanted to supplement my existing rules with code so that I can quickly move things into specific folders in an ad-hoc fashion. In fact, I am increasingly shying away from rules these days, as I believe I’ve noticed a correlation between the use of rules (of which I currently have about 6) and the noticeable performance hit my machine often takes when Outlook receives mail and runs through all the rules. (At the risk of sounding overly cynical, I seem to have noticed that whenever my machine temporarily stops responding or when it seems to freeze, it almost always coincides with Outlook “receiving” mail from the Exchange server and running the rules I have set up.)

Again, thanks to you both for the help.

Even though I only have IE7 installed (to my knowledge), I read that article hoping it would uncover something, but alas, my configuration was just as they would have me set it. But I did notice one other thing that I THOUGHT I noticed before but which seemed weird: if I open a Woody’s Lounge email and find that clicking on a link throws this “error,” I noticed that if I wait a minute or so (literally), the links will then work as expected.

I swear I am not making this up.

One other nice variable: our company uses a Conifguration Script for IE. I am not at all sure what it does, and I can’t imagine why it would touch any settings that would affect hyperlinks in an email (well, OK, I can imagine why in a company this large.) Nonetheless…

I guess I’ll never know for sure.

Now THIS is bizarre. Within 90 minutes of posting my last message (stating that I can’t duplicate the problem), guess what? I opened an email from the LoungeAdmin from yesterday (the March 19 “daily archive of VB / VBA”, to be precise) and the problem came up again! In between the time I said I couldn’t duplicate it and the time it happened again, the only significant things I remember that I did were 1) downloaded and installed the “Microsoft Office SharePoint Server 2007 Training (Standalone Edition)” msi, and watched a bit of YouTube!

Here’s a picture of the prompt. I’m at a loss.

OK, I’ve been watching the behavior of my machine since I worte this, and, as I expected, the problem has not resurfaced, no matter what I do!

First, a little clarification: the error I was getting was a prompt to select the executable to use to “open” the link. (It wasn’t, as I originally stated, a prompt to save something.)

That said, if anyone else gets that dialog box about what executable to use, I’d like to hear about it.

Thanks!

As ever, Hans, thanks for your wisdom and patience.

Also, check the document’s “Vertical Alignment” (found in the Layout tab under File: Page Setup). Normally, it should be set to “top.” (Having it set to “Center” will cause the phenomenon you describe.)