G
Guest
Our department uses an Access application for writing multimedia scripts. We
provide an "empty" copy of the database (both FE & BE in one mdb) to the
creative writer to draft a script, then the database is put on our server for
collaboration and production. Currently, each unique script (we have dozens)
is a separate database. We are having a great deal of difficulty managing
changes to the front end design of these databases because there are so many
copies of it (close to 100). I was thinking it might work better to split
the databases so we only have to maintain the one file. But we would need to
design it so so that the users could select which data source (script) they
wanted to work on. And since that data source could be on a server, or if
they were working from home, on their local drive, we would need to enable
them to browse (or enter the path) to the file they want to edit. Is this a
good idea - and if so, does anyone know how change the datasource of the
linked tables based on user entry?
provide an "empty" copy of the database (both FE & BE in one mdb) to the
creative writer to draft a script, then the database is put on our server for
collaboration and production. Currently, each unique script (we have dozens)
is a separate database. We are having a great deal of difficulty managing
changes to the front end design of these databases because there are so many
copies of it (close to 100). I was thinking it might work better to split
the databases so we only have to maintain the one file. But we would need to
design it so so that the users could select which data source (script) they
wanted to work on. And since that data source could be on a server, or if
they were working from home, on their local drive, we would need to enable
them to browse (or enter the path) to the file they want to edit. Is this a
good idea - and if so, does anyone know how change the datasource of the
linked tables based on user entry?