Adding email attachment causes PowerChurch to abort

[pbumc]

Hi,

We're running PowerChurch 10.4 with MR 02/07/2008.

I'm trying to send email messages to a Personal Profiles group. As soon as I click on the Attach button, PowerChurch aborts with this error:

PROGRAM: MAILASSIST.PGFASSIST.PAGE8.CCOMMANDGROUP1.COMMAND1.CLICK
LINE: 31
ERROR: 202
MESSAGE: Invalid path or file name.

Note that this happens _before_ I see a file dialog, so I have not yet specified a path or file name.

How do we fix/work around this issue?

Thank you,

Mark Berry

[Zorak]

Apparently, the issue here is that the folder that Windows is referencing as this User Account's "My Documents" folder does not exist.

We have been able to recreate this error by renaming or moving the My Documents folder.

I have written this up as a bug that will be addressed in a future Maintenance Release, we need to look for a different folder, or just open the current Program Directory, rather than showing an error.

[pbumc]

Thank you for your message!

All computers here do have a _virtual_ My Documents folder. However, I have implemented Folder Redirection on this network. This means that My Documents are actually stored on the server, although to the user it looks like it is local. It's a pretty cool feature since My Documents automatically get backed up during the daily server backup.

I'm emailing some notes on finding My Documents programmatically. I'll look forward to the fix!

Best regards,

Mark Berry

[pbumc]

This turned out to be a permissions issue due to the way PowerChurch checks for folder access rights.

When My Documents is redirected to the server, by default, users are allowed to access their own My Documents folder, but not to see the list of all users' folders.

When PowerChurch checks for the My Documents folder, it does so by first going to its parent folder, then checking to see if My Documents exists before changing to the My Documents folder. With folder redirection, since normal users are not allowed to list the folders in the parent folder, an access violation occurs.

I was able to work around the problem by going to the parent folder on the server and granting the List Folder permission to authenticated users.

It would still be nice that if opening My Documents fails for some reason, PowerChurch would fall back to another folder, perhaps the PowerChurch program directory, rather than aborting the program. It would also help if the dialog would remember the folder from one time to the next. (We'll always be attaching newsletter PDF files out of the same folder.)

Regards,

Mark Berry

[Zorak]

Thanks, Mark. We have this written up as a bug and it will be addressed.