faeryfyrre
Programmer
Hi Guys,
I'm in need of some advice. I have a database which stores Employee Commission information. For audit purposes i need to store some emails as proof of approval by Employee's supervisors. Now each record needs to store 10 approval emails and there will be approx 200 records added annually.
This database must run in a multiuser-network environment and i was wondering whether the size of these records is likely to slow Access down noticably?
Now i could just store the emails in a central folder on the server and link to them but this organisation is renown
for changing it's directory structure almost yearly and all my links to the emails would break (meaning i would have to write a routine that fixes broken links). Therefore i feel that Embedding is the preferable option but i am concerned with performance issues.
Your incite is appreciated.
Alec Doughty
Doughty Consulting P/L
"Life's a competition. Play hard, but play fair"
I'm in need of some advice. I have a database which stores Employee Commission information. For audit purposes i need to store some emails as proof of approval by Employee's supervisors. Now each record needs to store 10 approval emails and there will be approx 200 records added annually.
This database must run in a multiuser-network environment and i was wondering whether the size of these records is likely to slow Access down noticably?
Now i could just store the emails in a central folder on the server and link to them but this organisation is renown
for changing it's directory structure almost yearly and all my links to the emails would break (meaning i would have to write a routine that fixes broken links). Therefore i feel that Embedding is the preferable option but i am concerned with performance issues.
Your incite is appreciated.
Alec Doughty
Doughty Consulting P/L
"Life's a competition. Play hard, but play fair"