 |
|
|
|
Next: Simple setup but failed to connect
|
| Author |
Message |
External
Since: Oct 23, 2006
Posts: 236
|
(Msg. 31) Posted: Wed Dec 31, 2008 3:56 am
Post subject: Re: Split Database Pros and Cons [Login to view extended thread Info.]
Archived from groups: comp>databases>ms-access (more info?)
|
|
|
if you want to support multiple users and be able to adjust your
schema while people are using this data-- then you're forced to move
to SQL Server.
Jet has -ZERO- capability for uptime
On Dec 24, 8:01 am, "Donald Calloway" wrote:
> I'm hoping someone can answer these questions for me.
>
> As I understand the split database arrangement, the back-end is all
> that gets transmitted via the network when data are created, modified or
> deleted, whereas the front-end is the non-changing aspect of the RDBMS that
> resides on each multi-user client PC: forms, queries, reports, macros and
> modules.
> The database fingerprint on the shared server would thus consist of only
> the data,
> and would be considerably smaller than the totality of the database that
> resides there now.
>
> Now for my first question: Aside from speeding up data transfer, what
> other advantages would I hope to realize in a multi-user environment?
>
> Now my second question: In a split-database scenario with multi-user
> environment,
> if I need to make changes to the functionality of the database or some
> cosmetic
> improvements; for example, updating a form's appearance or modifying its
> functionality, or improving on the design of a query, macro, report, etc.,
> would I not have to deploy the changes to all client PCs individually
> rather
> than the way it is handled now, i.e., taking the system down, making the
> changes
> and then bringing the system back on line?
>
> --
> Using Opera's revolutionary e-mail client:http://www.opera.com/mail/ |
|
| Back to top |
|
 | |
External
Since: Apr 16, 2008
Posts: 174
|
(Msg. 32) Posted: Wed Dec 31, 2008 4:21 am
Post subject: Re: Split Database Pros and Cons [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Hmmmm. I guess I have used "splitting databases" to include using
ADPs, and, after further review of the memory banks I think the ADP
route is the route I almost always took, as opposed to two mdb type
files.
Right now I am experimenting with disconnected ADPs using persisted
XML files for data storage.
I get the superior power of the ADP, the huge (relative to DAO) object
model of ADO, a very small footprint in terms of file size, and
startling speed. Of course,these are suitable only for small projects.
On Dec 31, 6:47 am, " "
wrote:
> lyle;
>
> well I started upsizing databases to Access Data Projects 9 years ago.
> On Dec 30, 3:33 am, lyle fairfield wrote:
> > I think I started splitting databases and distributing individual
> > front ends to users, as a rule, about nine years ago. |
|
| Back to top |
|
| |
External
Since: Dec 24, 2008
Posts: 14
|
(Msg. 33) Posted: Wed Dec 31, 2008 7:25 am
Post subject: Re: Split Database Pros and Cons [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
You would perhaps become a bit tactless or lose diplomacy yourself if you
had been called a troll and a lier like I was.
On Tue, 30 Dec 2008 01:00:59 -0500, Larry Linson
wrote:
> "Wayne" wrote
>
> > Good to see that David hasn't lost any of his tact and diplomacy. 
>
> Nor Donald, either, I note.
>
>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ >> Stay informed about: Split Database Pros and Cons |
|
| Back to top |
|
| |
External
Since: Nov 15, 2007
Posts: 1217
|
(Msg. 34) Posted: Thu Jan 01, 2009 12:25 am
Post subject: Re: Split Database Pros and Cons [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
"Donald Calloway" wrote:
>My office has used an application, which I personally developed, in a
>multi-user environment (with c. 25 simultaneous users at any one time) for
>about two years now with little to no problems encountered. It is not
>deployed as a FE/BE, rather the linked databases reside on the shared
>server.
There have been occasional credible postings of a non split A2000 or newer working
successfully. I'm greatly puzzled as to how such can successfully work. <smile>
Now I'd never do that especially given that maintaining the FE would be significantly
more difficult. Which is the biggest reason I created the Auto FE Updater in the
first place.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ >> Stay informed about: Split Database Pros and Cons |
|
| Back to top |
|
| |
External
Since: Dec 24, 2008
Posts: 14
|
(Msg. 35) Posted: Thu Jan 01, 2009 10:25 am
Post subject: Re: Split Database Pros and Cons [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
Mine is credible, let me assure you of that. I also have developed, and
succesfully used for over a year now, a non-split A2000 database which
employs User/Group permissions (in the workgroup file) vs. a single
database password for database security purposes. I've likewise enjoyed
virtually no issues with this non-split database in a year's time.
On Wed, 31 Dec 2008 23:43:21 -0500, Tony Toews [MVP]
wrote:
> "Donald Calloway" wrote:
>
>> My office has used an application, which I personally developed, in a
>> multi-user environment (with c. 25 simultaneous users at any one time)
>> for
>> about two years now with little to no problems encountered. It is not
>> deployed as a FE/BE, rather the linked databases reside on the shared
>> server.
>
> There have been occasional credible postings of a non split A2000 or
> newer working
> successfully. I'm greatly puzzled as to how such can successfully
> work. <smile>
>
> Now I'd never do that especially given that maintaining the FE would be
> significantly
> more difficult. Which is the biggest reason I created the Auto FE
> Updater in the
> first place.
>
> Tony
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ >> Stay informed about: Split Database Pros and Cons |
|
| Back to top |
|
| |
External
Since: Nov 17, 2008
Posts: 66
|
(Msg. 36) Posted: Thu Jan 01, 2009 10:25 am
Post subject: Re: Split Database Pros and Cons [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
On Thu, 01 Jan 2009 14:29:45 +0000, Donald Calloway wrote:
> Mine is credible, let me assure you of that. I also have developed, and
> succesfully used for over a year now, a non-split A2000 database which
> employs User/Group permissions (in the workgroup file) vs. a single
> database password for database security purposes. I've likewise enjoyed
> virtually no issues with this non-split database in a year's time.
Frankly the whole file corruption thing is like making backups to guard
against hard drive failures. If you've never had a drive fail then you
are a lot less likely to do backups and a lot less likely to think it's a
big deal. Most people eventually get burned though and it is completely
anecdotal.
In my opinion there a tremendous advantages to splitting that have zero
to do with file corruption so why anyone would NOT split is a mystery to
me.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com >> Stay informed about: Split Database Pros and Cons |
|
| Back to top |
|
| |
External
Since: Dec 24, 2008
Posts: 14
|
(Msg. 37) Posted: Thu Jan 01, 2009 10:25 am
Post subject: Re: Split Database Pros and Cons [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
I may have an impediment to splitting; let me explain. Since I have two
non-split databases which are already linked, how would I go about
splitting the two databases so they are still linked after the split?
On Thu, 01 Jan 2009 10:00:24 -0500, Rick Brandt
wrote:
> On Thu, 01 Jan 2009 14:29:45 +0000, Donald Calloway wrote:
>
>> Mine is credible, let me assure you of that. I also have developed, and
>> succesfully used for over a year now, a non-split A2000 database which
>> employs User/Group permissions (in the workgroup file) vs. a single
>> database password for database security purposes. I've likewise enjoyed
>> virtually no issues with this non-split database in a year's time.
>
> Frankly the whole file corruption thing is like making backups to guard
> against hard drive failures. If you've never had a drive fail then you
> are a lot less likely to do backups and a lot less likely to think it's a
> big deal. Most people eventually get burned though and it is completely
> anecdotal.
>
> In my opinion there a tremendous advantages to splitting that have zero
> to do with file corruption so why anyone would NOT split is a mystery to
> me.
>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ >> Stay informed about: Split Database Pros and Cons |
|
| Back to top |
|
| |
External
Since: Nov 17, 2008
Posts: 66
|
(Msg. 38) Posted: Thu Jan 01, 2009 11:32 am
Post subject: Re: Split Database Pros and Cons [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
On Thu, 01 Jan 2009 15:20:13 +0000, Donald Calloway wrote:
> I may have an impediment to splitting; let me explain. Since I have two
> non-split databases which are already linked, how would I go about
> splitting the two databases so they are still linked after the split?
Pretty much the same as splitting any other file (if you don't use the
wizard).
Make two copies of FileA. In one copy (FileA_FE) delete all tables and
links). In the other (FileA_BE) delete everything except local tables.
Do the same thing with your other file creating FileB_FE and FileB_BE.
In FileA_FE make links to all of the tables in FileA_BE as well as links
to any tables you need from FileB_BE.
In FileB_FE make links to all of the tables in FileB_BE as well as links
to any tables you need from FileA_BE.
--
Rick Brandt, Microsoft Access MVP
Email (as appropriate) to...
RBrandt at Hunter dot com >> Stay informed about: Split Database Pros and Cons |
|
| Back to top |
|
| |
External
Since: Nov 15, 2007
Posts: 1217
|
(Msg. 39) Posted: Thu Jan 01, 2009 5:25 pm
Post subject: Re: Split Database Pros and Cons [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
"Donald Calloway" wrote:
>I may have an impediment to splitting; let me explain. Since I have two
>non-split databases which are already linked, how would I go about
>splitting the two databases so they are still linked after the split?
Whoops, I see another outstanding question on this same topic but Rick has answered
your question.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/ >> Stay informed about: Split Database Pros and Cons |
|
| Back to top |
|
| |
External
Since: Dec 24, 2008
Posts: 14
|
(Msg. 40) Posted: Thu Jan 01, 2009 8:25 pm
Post subject: Re: Split Database Pros and Cons [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
You gave me the answer I needed, as I couldn't figure out how to make it
work using the Wizard. Thanks a bunch.
On Thu, 01 Jan 2009 10:50:38 -0500, Rick Brandt
wrote:
> On Thu, 01 Jan 2009 15:20:13 +0000, Donald Calloway wrote:
>
>> I may have an impediment to splitting; let me explain. Since I have two
>> non-split databases which are already linked, how would I go about
>> splitting the two databases so they are still linked after the split?
>
> Pretty much the same as splitting any other file (if you don't use the
> wizard).
>
> Make two copies of FileA. In one copy (FileA_FE) delete all tables and
> links). In the other (FileA_BE) delete everything except local tables.
>
> Do the same thing with your other file creating FileB_FE and FileB_BE.
>
> In FileA_FE make links to all of the tables in FileA_BE as well as links
> to any tables you need from FileB_BE.
>
> In FileB_FE make links to all of the tables in FileB_BE as well as links
> to any tables you need from FileA_BE.
>
>
--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/ >> Stay informed about: Split Database Pros and Cons |
|
| Back to top |
|
| |
External
Since: Nov 17, 2007
Posts: 1157
|
(Msg. 41) Posted: Thu Jan 01, 2009 11:25 pm
Post subject: Re: Split Database Pros and Cons [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)
|
|
|
|
|
| Back to top |
|
| |
| Related Topics: | Access Split Database - Others cannot lauch database from .. - I have an access database that has been split and resides in the network share. When the access database is currently being updated by someone, and I try to open the database, I cannot open the file by double clicking on the database filename, for..
Split Database - I continue to get invalid arguements when i am trying to split my database. I have does this many time before and it always went smoothly. I have no idea what common problems would cause invalid arguement when trying to split a database. I am just tryin...
Rejoining a split database - How? - Hi All I have taken over a split database, originally done in MS Access 2000 The front end is in Access and the back end consists of an Access database What is the best way to rejoin this? I want to have just one proect on my dev machine with a view....
Transfering a split database - I am working on a database in ACCESS 2003. This is a simple DB with only one table. I have successfully split the database into database.mdb and database_be.mdb. When I copy the two files to a clients' computer and try to run database.mdb I receive th...
Modify split database - I have a split database that acts as a call log. The back end consists of a table with over 2,000 records and the front end contains a form that multiple users fill out. My company has decided to change the requirements of the call log table and has... |
|
You can post new topics in this forum
You can reply to topics in this forum
You can edit your posts in this forum
You can delete your posts in this forum
You can vote in polls in this forum
|
|
|
|
|
|
|
FAQ
Search
Profile
Private Messages
Log in
