moke123
AWF VIP
- Local time
- Today, 04:31
- Joined
- Jan 11, 2013
- Messages
- 4,683
Here's an example i made for someone on another forum.
It does not store the path to any files.
when the database is opened it creates a folder named Clients in the same folder as the database.
When you enter a new client and open the client form, it will create a folder for that client within the Clients folder.
When you save a file for a client you save it to their particular folder.
When you open the client detail form, a procedure runs which lists all the files in that folder in a listbox. Double clicking the list will open the file.
So long as the Clients folder and the subfolders are in the same folder as the database you don't have to store any file paths.
note that in the demo if you use the get file button to add a file it is copying the file to the folder as opposed to moving it to the folder so deleting it won't delete the original file.
It does not store the path to any files.
when the database is opened it creates a folder named Clients in the same folder as the database.
When you enter a new client and open the client form, it will create a folder for that client within the Clients folder.
When you save a file for a client you save it to their particular folder.
When you open the client detail form, a procedure runs which lists all the files in that folder in a listbox. Double clicking the list will open the file.
So long as the Clients folder and the subfolders are in the same folder as the database you don't have to store any file paths.
note that in the demo if you use the get file button to add a file it is copying the file to the folder as opposed to moving it to the folder so deleting it won't delete the original file.