User's Desktop: Locked Down?

[PeteCresswell]

I've been changing my apps to be compliant with MS's standard of
writing temp data only to C:\Documents And Settings\[UserName]....

But now I'm converting an app that creates .TXT files and spreadsheets
for the user.

Making them navigate to C:\Documents And Settings\[UserName].... seems
needlessly onerous if I can write those files to their desktop.

So, am I within the rules if I write a persistant/non-temp file that
the user requests to their deskdop?

[Trevor Best]

PeteCresswell wrote:

I've been changing my apps to be compliant with MS's standard of
writing temp data only to C:\Documents And Settings\[UserName]....

But now I'm converting an app that creates .TXT files and spreadsheets
for the user.

Making them navigate to C:\Documents And Settings\[UserName].... seems
needlessly onerous if I can write those files to their desktop.

So, am I within the rules if I write a persistant/non-temp file that
the user requests to their deskdop?

I generally write things to the temp folder (Environ("TEMP" )) and the
users can navigate there eaily using "%TEMP%".

I would eventually get p*ssed off if a load of icons suddenly covered up
Rebecca Romijn on my desktop :-)

Have you thought about storing a profile of where to write files to so
that user chooses the destination? For things like purchase orders,
which I generate in Word, I save these to a predefined place on the network.

[(PeteCresswell)]

Per Trevor Best:

Have you thought about storing a profile of where to write files to so
that user chooses the destination? For things like purchase orders,
which I generate in Word, I save these to a predefined place on the network.

No. But I was being thoughtless...

With the allergy season in full force, it's taking more and more coffee to get
my IQ above room temperature...

I think that's the answer: A little confirmation prompt with a default path and
a Common Dialog behind a "Change Destination" button.
--
PeteCresswell