Hi Edgar,
A split database actually makes your database modifications easier. One of the major reasons to use a split database is so that you can make changes to your front end forms, reports, queries and code and save it but your data remains safely untouched in the back end tables. Then you just use or distribute the new front end which will use the unchanged back end.
If you need to make changes in the tables in the back end you can do that and then link or relink the tables to the front end.
Kind Regards,
Pat Wood
http://accesstips.wordpress.com
--- In MS_Access_Professionals@yahoogroups.com, "rivera_vazquez_edgar" <xtintores@...> wrote:
>
> Pat, the thing is, I need to make mayor changes on the database design but there a re some changes that I can not do because parts of the front end seem to be locked. I actually made a new database instead of making changes to the existing one but there is just too much data to be re entered into the new database. I rather make changes to the existing database and just work around the data without loosing it. That's why I wanted to unsplit it, to make it easier to modify it.
>
> Edgar
>
> --- In MS_Access_Professionals@yahoogroups.com, "patrickawood" <pwood57@> wrote:
> >
> > Hi Edgar,
> >
> > IMO It is not worth it to go through the trouble of making it a single database file. The database will work perfectly well as a split database and if it is on the same drive as the front end you will almost certainly not notice any difference in performance.
> >
> > Kind Regards
> > Pat Wood
> > http://accesstips.wordpress.com
> >
> > --- In MS_Access_Professionals@yahoogroups.com, "rivera_vazquez_edgar" <xtintores@> wrote:
> > >
> > > Ok, but now, how do I take a database that has already been splited and join it back together?
> > >
> > >
> > > --- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@> wrote:
> > > >
> > > > > Unless you have other files associated with the front end there is
> > > > >no need to install anything.
> > > >
> > > > I should have said, "Provided your users all have Access installed, there is nothing to install at the users' end."
> > > >
> > > > Bill
> > > >
> > > >
> > > > --- In MS_Access_Professionals@yahoogroups.com, "Bill Mosca" <wrmosca@> wrote:
> > > > >
> > > > > Edgar
> > > > >
> > > > > There is a database tool in Access to split the database for you. Once you split it you can move the back end (tables only) to a shared folder on your server.
> > > > >
> > > > > Each user gets a copy of the front end. I always make my front ends MDE files (or ACCDE files if using 2007 or 2010). MDEs and ACCDEs are compiled and do not let users make design changes to forms, reports, macros and code.
> > > > >
> > > > > Any design changes are made in your MDB front end and a new MDE is made for your users. Therefore, it is imperative that you keep your MDB safe and have good backups.
> > > > >
> > > > > There are other steps to take like setting database properties to hide menus, disallow shortcuts, etc. See my sample StartUpFormForMDE.zip in the Files/Samples folder here.
> > > > >
> > > > > Unless you have other files associated with the front end there is no need to install anything.
> > > > >
> > > > > See my article on deploying and updating front ends at:
> > > > > http://thatlldoit.com/howtosarticles.aspx#fe_updater
> > > > >
> > > > > Regards,
> > > > > Bill Mosca, Founder - MS_Access_Professionals
> > > > > http://www.thatlldoit.com
> > > > > Microsoft Office Access MVP
> > > > > https://mvp.support.microsoft.com/profile/Bill.Mosca
> > > > >
> > > > >
> > > > >
> > > > > --- In MS_Access_Professionals@yahoogroups.com, "rivera_vazquez_edgar" <xtintores@> wrote:
> > > > > >
> > > > > > Ok, the database is preaty much done. now how do I plit the data from the front end and seal the proyect to be installed on local disk C like any other program?
> > > > > > Edgar
> > > > > >
> > > > >
> > > >
> > >
> >
>
Tidak ada komentar:
Posting Komentar