S
SteveS
Hi all,
I'm posting my database (2003 mde format) to an internal sharepoint site.
However, I got the suggestion in a previous post (on securing my db) that
before creating my mde file I should split the database. Since I'm putting it
on sharepoint and the back-end would not be available on a network drive for
others to link to, I don't think this would work for me. However, I wanted to
put it out there since I'm relatively new to Access and this is my first
database.
Is there a reason I should split my database, and how could I share this
with my geographically dispersed co-workers if the back-end isn't accessible
on a network drive? I assume they wouldn't be able to do much with just the
front-end on sharepoint... and I don't know what benefit there would be of
posting the front-end and back-ends separately on the sharepoint site.
Any and all input is welcome!
Thanks!
I'm posting my database (2003 mde format) to an internal sharepoint site.
However, I got the suggestion in a previous post (on securing my db) that
before creating my mde file I should split the database. Since I'm putting it
on sharepoint and the back-end would not be available on a network drive for
others to link to, I don't think this would work for me. However, I wanted to
put it out there since I'm relatively new to Access and this is my first
database.
Is there a reason I should split my database, and how could I share this
with my geographically dispersed co-workers if the back-end isn't accessible
on a network drive? I assume they wouldn't be able to do much with just the
front-end on sharepoint... and I don't know what benefit there would be of
posting the front-end and back-ends separately on the sharepoint site.
Any and all input is welcome!
Thanks!