pr2-eugin
Super Moderator
- Local time
- Today, 09:33
- Joined
- Nov 30, 2011
- Messages
- 8,494
Hello !
I have been trying to figure out a best way to attach files to specific records. Up until this point have been using Hyperlink to link files that have been stored in shared folders. This seemed to be a very good option for quiet sometime; but some users wish to play god ! Since I have to give them RWX permission on the folder; they go into the Shared folder and either rename the file or move it around or worse, DELETE the file permanently. Thus messing up the hyperlink.
Now I am planning to use the wretched Attachment data type in Access. I know it will bloat the DB, but this seems to be a safer option. As I can control DELETES/EDITS. So I was thinking to use a stand alone DB, just used for Attachment tables. As these records will not be accessed everytime.
My problem is, I remember vaguely using two linked backend DB files, put a lot of strain on the front end. Thus making the connection very slow. Sometime even upto 10 seconds to simply load the login form.
My idea is to establish a persistent connection to the two DB files on front end opening. Thus the connection is always there so it might not be that slow !
Or is there something I could look into to manage the Files/Attachments more efficiently, other than Hypelinking? Cheers for any ideas.
I have been trying to figure out a best way to attach files to specific records. Up until this point have been using Hyperlink to link files that have been stored in shared folders. This seemed to be a very good option for quiet sometime; but some users wish to play god ! Since I have to give them RWX permission on the folder; they go into the Shared folder and either rename the file or move it around or worse, DELETE the file permanently. Thus messing up the hyperlink.
Now I am planning to use the wretched Attachment data type in Access. I know it will bloat the DB, but this seems to be a safer option. As I can control DELETES/EDITS. So I was thinking to use a stand alone DB, just used for Attachment tables. As these records will not be accessed everytime.
My problem is, I remember vaguely using two linked backend DB files, put a lot of strain on the front end. Thus making the connection very slow. Sometime even upto 10 seconds to simply load the login form.
My idea is to establish a persistent connection to the two DB files on front end opening. Thus the connection is always there so it might not be that slow !
Or is there something I could look into to manage the Files/Attachments more efficiently, other than Hypelinking? Cheers for any ideas.
Last edited: