File references

[tklusmeyer]

I wish to create a database that has a field that references a filename. Should this be a character field? I prefer that when a user enter a filename that they could select a browse tool to search their system for the file for which they would like to reference. Upon selection of the file the proper file name would show up in the field with the correct path syntax. If the user selects to type in the path, then validation should take place to ensure that the syntax is correct.

[mheller]

Re: File references

Web or desktop?

[Mike Wilson]

Re: File references

Martin,
This is why this MB category is confusing. Maybe New Developer, Web and New Developer, Desktop?

[tklusmeyer]

Re: File references

My question is for desktop applications. I have the need for users to browse and select a file and then for the database to store the file in a safe location for the user to retrieve and view it later. The file may or may not be a .pdf, xls, doc, or image file. The database application would have to open the application associated with the file that is stored in order to view the file contents.

I thought this would be simple but I'm challenged to find sample or template applications or information in HELP for information on file handling. I suspect I'm just looking in the wrong place.

Any help appreciated!

[tklusmeyer]

Re: File references

I'm not sure if I'm clear here, so I will elaborate. I'm trying to create a file management database for some cad files that get created by my associates. The user would use the application to select a file on their system and the database application would take the file and move it to an archive location and associate it with various data. I expected this to be a simple thing but apparently I'm looking in the wrong place for examples of how to deal with simple file processing. I assume that the record in the database would identify the location for which the file gets stored.

I have little experience using a database program like this. My experience has been with Webex Office databases where there are data types called "file attachments" which keeps this very simple. I suspect that this will be a bit harder for me in Alpha5. I hope not!

Thanks to any helpers!!

[Al Buchholz]

Re: File references

So where in Wisconsin r u?

[Stan Mathews]

Re: File references

so I will elaborate

Keep working on that.

I have the need for users to browse and select a file

Alpha has a function named, oddly enough, ui_get_file() which allow you to accept input from a user specifying a file and its location merely by navigating to it..

then for the database to store the file in a safe location

Taking the input mentioned above you can use file.copy() to archive it where you will.

associate it with various data

Sorry, don't have a clue what that means. If you possibly mean rename the file to associate it with a particular "id_number" or name, that can be part of the copy process.

All relatively simple.

[Stan Mathews]

Re: File references

Here's a pretty simple locate and store somewhere else example.

[tklusmeyer]

Re: File references

Here's a pretty simple locate and store somewhere else example.

Thanks, Stan. I'll check out your suggestions!

[Stan Mathews]

Re: File references

Bit more here to record the archived file to the current record and allow the user to choose one to open.

[tklusmeyer]

Re: File references

Bit more here to record the archived file to the current record and allow the user to choose one to open.

Thanks, Stan. It took me awhile to figure out what you did and I think I understand it. I checked out your "test" form and it's close to what I want.

I think what I want is this:
1. The user would navigate to the field (ref) in the form and upon clicking into the field a "file open" dialog box would pop up.
2. The user could navigate to find the file they wish to store and then they would press the open button.
3. The file would save to the archive folder as you defined ("C:\temp\archive").
4. The filename would appear in the field (ref) without any reference to its path.
5. If the filename is not unique, the database would define it uniquely but this would be hidden from the user (only the filename for which the user originally entered would be displayed in the field).
6. Whenever the user returns to this particular field in the record they could open and view the file (perhaps this can only be done in a form with a button rather than a browse). If the file-type is associated in windows components, then the program would start and open the file. If the file-type is not associated, then the user could select the "open with" dialog if they wanted.

I don't know if this is the best approach but it seems practical to me. Any thoughts?

Thanks for your awesome examples!

[tklusmeyer]

Re: File references

So where in Wisconsin r u?

I'm in Sun Praire, northeast of Madison. Regards!

[Al Buchholz]

Re: File references

I'm in Sun Praire, northeast of Madison. Regards!

Excellent. We're almost neighbors. Or within an hour or so..

[Stan Mathews]

Re: File references

I don't know if this is the best approach but it seems practical to me. Any thoughts?

I don't see anything in your outline that seems troublesome but it will be Monday before I have a chance to revisit the issue.

If the filename is not unique

I assume you mean filename and extension. One might save this_customer.pdf, this_customer.dat, this_customer.xls, etc.

[tklusmeyer]

Re: File references

I don't see anything in your outline that seems troublesome but it will be Monday before I have a chance to revisit the issue.


I assume you mean filename and extension. One might save this_customer.pdf, this_customer.dat, this_customer.xls, etc.

Thinking about the filename issue, perhaps it makes sense to name the file the same as the record_ID in the database followed by its extension. So, the filename might be record_ID.pdf, record_ID.xls, etc. This way, the filename will truly be unique.

Thanks for your input. I'm looking forward to your thoughts.