[AccessD] Storing Files in Directories

Not sure where you are having problems.

Code produces data, which you write to file in appropriate place (checking
for existance of path...creating as necessary).  File written, open file for
editing in Word.  File is already saved in correct place with correct name,
so the default 'save' in Word will write to the same spot.

Drew

-----Original Message-----
From: Arthur Fuller [mailto:artful at rogers.com]
Sent: Thursday, August 18, 2005 1:02 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Storing Files in Directories


The current client has distinct preferences about how files ought to be
stored. 

A client has 1:M projects.
A project has 1:M assessments.
An assessment concerns exactly one workstation.
The resulting document must come out reflecting all workstations involved in
said project for said client (this part is trivial).

The client app's native directory is c:\MyClient. The subdir for said
reports is c:\MyClient\reports.

The client wants me to create a dir for each project and then plant the
related documents in said project-subdir.

This says to me that the Client table contains a directory name, and that
the ClientProjects table also contains a directory name, and that given
project 12356 I concatenate the above two values, plus the unique
identifier, and create a file called "c:\MyClient\HerClient\Reports\" &
Unique_ID & ".doc" (the resultant docs are all Word files).

1. I have so far created the said doc from a template: no problems there.
But I would like also to supply the concatenated filename so that a simple
click on the Save button causes the file to be saved. (I should mention that
the docs spit out by the Access app _always_ require editing; else we would
simply dump an Access report.)

Given that the client is CharlotteFoust and that her docs get sent to
c:\MyClient\HerClient\CharlotteFoust, then I want Word to realize that the
created document should be called "c:\MyClient\HerClient\CharlotteFoust\" &
Unique_ID & ".doc" -- and placed in subdir (create if required) Project
20050818.

I don't want the user to have to name the file. I want that to have already
been done, so she can click Save after her edits and that's that.

Had I been granted the discretion to design this particular model, I would
not have chosen this path. That however is not the issue. The issue is that
the client and her employees want to do it this way. 

Advice, guidance, assaults on the model, all gratefully accepted.


-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com