File Upload

[SierraJuliet]

Without boring or confusing people with the reasoning, here is the following.

1. On different forms (not all) is an upload button.

2. There is an upload form for selecting a file and a folder.

3. The user selects the file for uploading and desired output directory.

4. When the save button is pressed the file is appended to the folder directory (i.e. saved in the directory).

The following is an example of what is occurring.




The end-state actually would be a text file that is read by the upload form for its' default directory rather than the user navigating to and selecting one each time, as this increases chance of error.

I am sure someone has already done this in the past so figured I would ask.

I found this from Allen Browne, which will come in handy for evaluating whether a file or folder already exists. http://allenbrowne.com/func-11.html

[June7]

What is the exact issue?

[SierraJuliet]

text file that is read by the upload form for its' default directory rather than the user navigating to and selecting one each time

[SierraJuliet]

In the main folder are the following:

C:\MainFolder
>frontend
>backend
>textfilefordirectory

[June7]

The form code is capturing a default path and loading as destination? You want something else to happen - user should select path? Use Windows FileDialog object.

[SierraJuliet]

Already using file dialog. The issue is saving the file to the selected destination and since there are variables the ideal method is to read the destination directory from a text file. This way the user selects the file and everything else is transparent when the save button is clicked. I had the file select and save working before but removed it. Now I am trying to add it back with the addition of a text file that contains the default directory for where it is to be saved. Mind is not cooperating with setting it up so I figured someone else may already have done this.

[June7]

Not sure what you are asking for. What determines the destination? If user is not to choose, then what rules determine where to save the file?

[SierraJuliet]

The point of the text file is not hard coding the directory into VBA. This way if someone decides to change where files are stored thereafter implementation then they may do so by changing the directory in the text file. That is really the only reason for having a text file.

The rules will be determined by what form they are located on when they open the file dialog, which will evaluate the form file number at that time and create the directory if it does not exist, which is the reason behind Allen Browne comment of original post. It is just irrelevant for this stage of fixing what I had working once upon a time

[SierraJuliet]

I will probably start as I usually do. Reading text file as string and then working outwards. This usually does the trick.

[ssanfu]

Consider:
Instead of a text file, I would use a table. That way there could be a form for adding/editing. The form could limit who can change the destination path.
A text file could be deleted and anyone could modify the text file.

[SierraJuliet]

Consider:
Instead of a text file, I would use a table. That way there could be a form for adding/editing. The form could limit who can change the destination path.
A text file could be deleted and anyone could modify the text file.

That is a great idea, why didn't I think of that. Plus it streamlines setting the default starting directory for all users more easily than changing each config file on each workstation.

[SierraJuliet]

So this is where I am at so far.

C:\MainFolder

>frontend
>backend

>>DirectoryConfigTable

The directory may be a local machine (not good), share drive (ok), or file server (better) for uploading files using the frontend as the interface.

[ssanfu]

Not sure what

C:\MainFolder

>frontend
>backend

>>DirectoryConfigTable

means, but if you have multiple users, EACH user should have a copy of the FE on their computer, the BE should be on a common accessible location, ie a shared drive or file server.
The "DirectoryConfigTable" (?) would be in the BE.


My $.02........

[June7]

I agree with Steve. If you want to allow ease of changing default path to use for a particular form, use a table to store path strings. The table can have a field to use as criteria for a DLookup().

[SierraJuliet]

Yes, the examples I gave were more for conceptual and not where the backend will actually be located.