Replies

I have found that Open Office is far more than adequate for home users. Free, updated, and powerful. How much collaboration goes on in a non-commercial setting?

The problem is with the batch files and such. The paths to the programs are hard-coded to a their XP-style path, C:Program Files…, so that the command line is built to execute the program with the file to open/run as an argument. The default installation on the new pc defaulted a lot of the programs I use to the 32-bit program files path, C:Program Files (x86). This invalidates nearly every batch file, script, etc. I have set up; it’s like my version of ‘Y2K’. None of my automations will run on the new pc because of this path issue; once I re-write the programs to use the new (x86) path they won’t work on my current pc; once I being the changeover everything has to be revised in one non-stop process. Or the programs can be re-installed to the path my automations expect.

With my experience with prior versions Windows, changing the install path has nearly always been an option during installation, and Windows has been compliant with non-standard locations. This 32/64 dual-path setup is relatively new to me, and I do understand there was probably a good reason for this split.

Re: E-mail address ‘aliases’ add security… “myname+windowssecrets@gmail.com” is really a pretty weak way to ‘disguise’ your email address. All a scoundrel needs to do is look for and eliminate everything from the ‘+’ to the ‘@’ and what do you get? “myname@gmail.com”. The so-called ‘secure’ email address is compromised.

I prefer Spamgourmet. I have an account there that redirects to my ‘protected’ address, and I can use the same sort of identifier tag with each website or vendor; windowssecrets.myname@spamgourmet.com. Similar to the gmail alias, but if the identifier tag is stripped out, myname@spamgourmet.com goes nowhere. If someone fakes an identifier I can get spammed, but the identifier is only good for a limited number of messages. I can specify @WindowsSecrets.com as a trusted sender and always get messages from that sender, and have anyone else using that identifier automatically ditched.

Anyone find any solutions for this? I’ve only started playing with email after all these years, and I’m experiencing the same thing. I wonder if it’s a function of the device you’re using. For example, Blackberry’s utilize real POP3, while other PDA type phones might be limited to email provided by web-based email (Gmail, Yahoo, etc.). I have found that I cannot utilize my own unix-based mail server as it is not web-based. I’ve not narrowed this done, so feel free to chime in…

What I’ve been able to determine is that this behaviour is an intentional feature built into Windows Mobile. During a Send/Receive any message in your Inbox that is not on your email server is removed, sort of an automatic cleanup. This is even documented in the manual for my phone (though who reads those,right?). The problem is email servers tend to get cleaned out – we have Outlook set to leave a copy of messages on the server, remove after 5 days.

I have a work-around that may help, but no solution. I created a ‘Saved’ folder and move incoming messages there so they are not available to be wiped during a Send/Receive. Not as convenient as having them in the Inbox but at least they are safe.

Got it working, thanks. I just had to tweak a little to strip non-printing characters off the end before I could pull the date from the line.

'Grab OrderDate
    OrderDateLine = Trim(ActiveDocument.Paragraphs(3).Range.Text)
    OrderDateLine = Left(OrderDateLine, Len(OrderDateLine) - 2)    'strip CR/LF
    OrderDate = DateValue(Right(OrderDateLine, 10))
    OrderDateStr = Format(OrderDate, "YYMMDD")

My code opens the file to inset page breaks, then save & archive the source and converted files. When archiving I put a datestamp on the file. Currently unable to read the date from the file itself I use the date the process is run:

'Save the file as a Word document
    ActiveDocument.SaveAs FileName:="DOLLY.DOC", FileFormat:=wdFormatDocument
    ActiveDocument.Close
    
'Copy the converted file to a date-stamped archive file
    FileCopy HomePath & "Dolly.doc", HomePath & "ArchiveConvertedDolly " _
        & Format(Now(), "YYMMDD") & ".doc"

There are two options here then, as I see it. I could capture the OrderDate value from the open file before the ‘ActiveDocument.Close’ command, or let the file close and read the date from the closed file (variable name = SourceFile), and then in either case use OrderDate in place of ‘Format(Now(), “YYMMDD”).

Both solutions seem to imply the file needs to be opened by the routine in order to read it. In the situation I am working with the file is already open. Would these work under this circumstance? Or, should I close the file, read it with your routine to extract the date, then re-open and continue my processing?

A little utility I use is The Wonderful Icon. Small in size, big in features, and absolutely .

Works nice, thanks.

My immediate desire is to be able to stop ‘Batchrun.exe’ – a batch control program that actually launches the Access program this bit of code would be used in. I want to test a condition, and then based on the results stop Batchrun and keep it from executing any more commands. Batchrun is set to run windowless when it is executing a batch, but in edit mode the window caption is ‘Batchrun’.

One mention comes from Lockergnome at http://www.lockergnome.com/nexus/windows/2…ips-and-tricks/%5B/url%5D, point #3:

---

Your software won

Such a simple solution!

Interesting solution, but a bit of an overkill for how I would be using the formula. I am intrigued with your ThisWorkbook subs – I’m sure I’ll find a use for them somewhere.

What setting is the BIOS using for Advanced Power Management? My hardware fully supports it, but Microsoft can’t detect the support, causing my installations to always fail at the exact same point — until I disabled the APM in the bios. Then the install went smoothly. Might be worth a try. The drawback is that I don’t have all the power management options I should have.

I currently have two pst folders open and would like to close one but can’t. I’ve followed the advice in this thread and have not found a solution. I had two entries for my Private.pst and deleted one and then the other; each time Outlook would refuse to let me close this pst. Then I deleted both at the same time. Outlook opened, I saw that a new entry was made in the Registry, and then Outlook refused to cooperate when I tried to close the pst. I restored the keys and when I opened Outlook I had duplicate Private.pst folders open.

A search of the entire registry failed to turn up any references to “mspst.dll”.

Attached is the Windows Messaging Subsystem section from my registry (as a .txt file). Since Outlook builds a new key when it is opened, perhaps it would all sort itself out if I get rid of the entire section?