After Splitting the database can I....

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Work on the backend while users have the front end open?
The FE will be for the users to view only. I have locked all the items on
the form, (text boxes, etc.).
However, I need to continue to add data to the BE that updates the FE, but I
wasn't sure if I could do that at the same time the users are viewing the FE.
Do I copy the BE, do updates & paste?
Thank you for your help.
 
You can certainly add data to the BE while other users have the FE open (in
fact, multiple users can add data simultaneously).

You won't be able to make design changes in the BE, though, if anyone's
currently got the database open. (Having the FE open doesn't always
correspond to having the BE open though: check whether there's a logging
file--the .ldb file--in the same folder as the .mdb to know)
 
However, I need to continue to add data to the BE

Since everyone else using their Front ends can update, and add data, then
for what reason would you think you can't?

So, yes....all users, including you can continue to add data. You can even
open the back end direct if you want but the whole idea with splitting was
do avoid more then one person in the back end.

Modifying tables structures is a complete different matter. In this case,
you WILL need to ask everyone to exit the application (or scheduling your
changes at a time when everyone is gone home). In this case, for testing,
and safety, I would make a copy of the back end, and then link my
development front end to this copy. That way, you can test deleting code,
and dangerous update code without trashing the production data.

If you modify a table, or add a new table to the "copy" of the back end,
then I simply make notes as to what I changed. I actually use note pad. I do
this so I don't forget what types of modifications I made.

Here is a sample


tblCustoers
added a new field called SalesRep (text 25)
added a new field called CreateDate (date/time field)


So, I make a notes on the above changes. Then, when it is time to deploy the
new next great version to my users, I will find a time when everyone is out
of the production back end. I will open up my notepad...and then implement
the list of modifying one by one (you do this by hand). I then link my new
great front end mdb to the production back end. You then create a mde, and
it is this mde that you distribute to each user (if you been missing any of
these steps, then you you missed how the development cycle works). This is
the standard approach you will use for development.

For reasons of testing your application, you really don't want to test on
the actually production database. So, you link to a copy of data and then
can test with such ease, and peace of mind. You can add, delete, test
without any worry.
 
Thank you so much.
I don't plan to make any design changes while users are viewing the FE, just
adding data is all I want to do.
Design changes will be done when no one is in the database.
So, that brings up another question. I will be making design changes at
some point. I know that I will do this when I'm the only one logged on, but
I will have to do that at the FE won't I?
So, once the changes are complete, will the users see those changes
immediately after they log in? Will I need to re-copy the FE to their
desktops?
 
Thanks for the help. I printed your article.
I'll be here tomorrow working on the split.
Have a wonderful weekend.
 
splitting MDB is the most ridiculous thing ever.

go ahead and move everything to ADP / MSDE or SQL Server; then you can
work on the backend whenever you want.

MDB is for babies; lose the training wheels!!
 
(e-mail address removed)> wrote in message
splitting MDB is the most ridiculous thing ever.
Click to expand...

you think so?
go ahead and move everything to ADP
Click to expand...

Oh, wait, you just said to use a ADP. That is EXACTLY THE same concept being
suggested here. A split database is where the data is MOVED OUT of
application part.

I have to wonder if your suggestion is one out of compete and utter
ignorance, or you really don't want to help people here?

I find it most ignorant that you state that splitting is stupid. Spitting
means that a person should move out the data from the application part. Then
you Mr. Ignorant comes along and suggests that a person should us a ADP.
Well, I hate to hurt your simple challenged brain, but suggesting to use a
ADP is to suggest that it is a good idea to move the data out of the
application part. This is a exactly what I suggested...

If you don't see the hypocrisy of your suggestion, then I would suggest that
your prescription meds are well over due, or you temporary run out of your
meds, and are in need of more. Time for some re-fills buddy, as I just
suggested to move the data out of the application, and you come along and
suggest the same thing!!
 
listen ****nut

splitting MDB is not really doing anything beneficial

go back to 3rd grade and learn a rela database
 
'oh im so cool because i have a real db "SERVER"' now that i keep one
mdb file somewhere else

YOU SHOULD BE SPENDING YOUR EFFORTS ON SOMETHING THAT IS RELEVENT IN
THE 21ST CENTURY.

MDB BECAME OBSOLETE THE DAY THAT ADP CAME OUT, THE FALL OF 99
 
I think you have anger issues, Aaron, because your posts range from truly
helpful to spiteful. The first time you ever responded to a question I
asked, you told me to "ditch MS Access and use SQL Server". That is probably
outstanding advice, except for the fact that I'm a temp who works for an
hourly wage. You want to know what influence I have over the software we
use? I'll give you a hint: You see it when you close your eyes.
My advice- breathe, count to 10, *then* post.
 
You must log in or register to reply here.

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

Split database 7
Distributing FE after splitting? 2
Citrix Deployment of Access 2007 Front End 0
Access 2003 app on Citrix server 9
Didn't convert FE to mde is that an issue? 2
Access split database 4
Error 3051 Help Please 6
Replication/Synching and Splitting 1

Back
Top