Splitting Database

[Konchetta via AccessMonster.com]

I have been reading some threads on splitting a database and just wanted to
know if it is necessary to do this for about 9 persons who will be using the
database. Will it still do what it needs to do without being split on a front
end and back end? Please advise and thanks for your assistance!!

 

[Douglas J. Steele]

Even if there's only one user, you should split into a front-end and
back-end, but it's critical when you've got more than one user. The chance
of database corruption increases exponentially when you have multiple users
in the same database.

Is there a specific reason why you're avoiding doing this?

 

[Konchetta via AccessMonster.com]

Thanks Mr. Steele. Yes there is a specific reason. Because I'm not a
programmer and not comfortable with trying to split the database. I'm afraid
I may really mess something up while trying to do this.

 

[Daniel Pineault]

The second you have more than 1 user you need to split your database! No
exceptions! It really isn't complicated to do, simply use the built in
database splitter.

Why are you trying to avoid doing this step?!?
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.

 

[Jack Leach]

YES!!!!

You should *always* split your db, even if you are the only one using it.
For more than one user, NOT splitting is opening the door to serious
corruption and a good chance of losing your entire project.


--
Jack Leach
www.tristatemachine.com

"I haven''t failed, I''ve found ten thousand ways that don''t work."
-Thomas Edison (1847-1931)

 

[Douglas J. Steele]

Splitting is extremely simple. It's difficult to mess up. And the benefits
far outweigh any potential issues. <g>

Make a copy of the application first, then either use the built-in Splitter
wizard, or follow the instructions Tony Toews has at
http://www.granite.ab.ca/access/splitapp/index.htm

 

[ryguy7272]

Good overview here:
http://www.granite.ab.ca/access/splitapp/index.htm
http://www.members.shaw.ca/AlbertKallal/Articles/split/
http://databases.about.com/od/tutorials/ss/splitaccessdb.htm

 

[Daniel Pineault]

You have nothing to worry about.

Before doing anything else, make a backup.
Then use the built-in database splitter. It take 2 seconds and it is all
done for you!

Just make sure you start by doing a backup and even if things go wrong (and
I don't see how that would happen) you simply go back to your backup and
start the process over. Backups are a database developer's best friend!!!
--
Hope this helps,

Daniel Pineault
http://www.cardaconsultants.com/
For Access Tips and Examples: http://www.devhut.net
Please rate this post using the vote buttons if it was helpful.

 

[Konchetta via AccessMonster.com]

Thank so much Mr. Steele. I really appreciate your assistance. Will make a
copy and try this. Thank you so much.

Splitting is extremely simple. It's difficult to mess up. And the benefits
far outweigh any potential issues. <g>

Make a copy of the application first, then either use the built-in Splitter
wizard, or follow the instructions Tony Toews has at
http://www.granite.ab.ca/access/splitapp/index.htm

Thanks Mr. Steele. Yes there is a specific reason. Because I'm not a
programmer and not comfortable with trying to split the database. I'm

[quoted text clipped - 16 lines]

 

[Konchetta via AccessMonster.com]

Thanks so much for your assistance. Will read ALL of this information.

Good overview here:
http://www.granite.ab.ca/access/splitapp/index.htm
http://www.members.shaw.ca/AlbertKallal/Articles/split/
http://databases.about.com/od/tutorials/ss/splitaccessdb.htm

Thanks Mr. Steele. Yes there is a specific reason. Because I'm not a
programmer and not comfortable with trying to split the database. I'm afraid

[quoted text clipped - 13 lines]

 

[Konchetta via AccessMonster.com]

Thanks a bunch Mr. Leach!!

YES!!!!

You should *always* split your db, even if you are the only one using it.
For more than one user, NOT splitting is opening the door to serious
corruption and a good chance of losing your entire project.

 

[Konchetta via AccessMonster.com]

I was afraid I would mess something up but Mr. Steele has given me some
instructions. Thanks for all your help!! Really appreciate this forum!!

 

[Konchetta via AccessMonster.com]

Thanks so much for your assistance!!

Good overview here:
http://www.granite.ab.ca/access/splitapp/index.htm
http://www.members.shaw.ca/AlbertKallal/Articles/split/
http://databases.about.com/od/tutorials/ss/splitaccessdb.htm

Thanks Mr. Steele. Yes there is a specific reason. Because I'm not a
programmer and not comfortable with trying to split the database. I'm afraid

[quoted text clipped - 13 lines]

 

[Konchetta via AccessMonster.com]

Thanks so much Mr. Pineault. I really appreciate this forum. You guys are so
much help!!

You have nothing to worry about.

Before doing anything else, make a backup.
Then use the built-in database splitter. It take 2 seconds and it is all
done for you!

Just make sure you start by doing a backup and even if things go wrong (and
I don't see how that would happen) you simply go back to your backup and
start the process over. Backups are a database developer's best friend!!!

Thanks Mr. Steele. Yes there is a specific reason. Because I'm not a
programmer and not comfortable with trying to split the database. I'm afraid

[quoted text clipped - 13 lines]

 

[Konchetta via AccessMonster.com]

Mr. Steele,

Should I use the SQL Server or the Access Database Splitter? I have Access
2007. I went to the link for Tony Toews but I didn't see the instructions.

Splitting is extremely simple. It's difficult to mess up. And the benefits
far outweigh any potential issues. <g>

Make a copy of the application first, then either use the built-in Splitter
wizard, or follow the instructions Tony Toews has at
http://www.granite.ab.ca/access/splitapp/index.htm

Thanks Mr. Steele. Yes there is a specific reason. Because I'm not a
programmer and not comfortable with trying to split the database. I'm

[quoted text clipped - 16 lines]

 

[Douglas J. Steele]

Did you try following the Overview link to
http://www.granite.ab.ca/access/splitapp/overview.htm ?

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/DJSteele
(no e-mails, please!)

Mr. Steele,

Should I use the SQL Server or the Access Database Splitter? I have
Access
2007. I went to the link for Tony Toews but I didn't see the instructions.

Splitting is extremely simple. It's difficult to mess up. And the benefits
far outweigh any potential issues. <g>

Make a copy of the application first, then either use the built-in
Splitter
wizard, or follow the instructions Tony Toews has at
http://www.granite.ab.ca/access/splitapp/index.htm

Thanks Mr. Steele. Yes there is a specific reason. Because I'm not a
programmer and not comfortable with trying to split the database. I'm

[quoted text clipped - 16 lines]

front
end and back end? Please advise and thanks for your assistance!!

 

[Konchetta via AccessMonster.com]

Yes sir I did. I will try it out today. I didn't understand that they were
instructions at first. Thanks

Did you try following the Overview link to
http://www.granite.ab.ca/access/splitapp/overview.htm ?

Mr. Steele,

[quoted text clipped - 15 lines]

 

[Konchetta via AccessMonster.com]

Hello Mr. Steele,

I completed the Splitting of my database. Not sure what will happen now.
I placed the BE on the agency's shared Z drive. Is that an ok location? And
the FE will be placed on each person's workstation. Is that okay as well?
Also, can a password be placed on the BE and FE? I already had one and was
wondering if I should remove it. Hope you get this posting. Thanks again!

Did you try following the Overview link to
http://www.granite.ab.ca/access/splitapp/overview.htm ?

Mr. Steele,

[quoted text clipped - 15 lines]

 

[Douglas J. Steele]

The location for the back-end sounds fine. Make sure that each user has a
minimum of Read, Write and eXecute on the folder where the back-end database
exists. For that matter, they should also have Delete (althought that's not
mandatory). This is the case even if you want them only to have read access
to the data: Access creates a locking file (.ldb or .laccdb) in the folder
where the database exists, and they need the ability to do that.

Passwords can be used if you want. To be honest, though, I've never worked
with passwords in Access, so I'm not sure whether anything needs changing to
accomodate them. If you're able to link the front-end to the back-end using
passwords, you'll probably be fine.

--
Doug Steele, Microsoft Access MVP
http://www.AccessMVP.com/DJSteele
(no e-mails, please!)

Hello Mr. Steele,

I completed the Splitting of my database. Not sure what will happen now.

I placed the BE on the agency's shared Z drive. Is that an ok location?
And
the FE will be placed on each person's workstation. Is that okay as well?
Also, can a password be placed on the BE and FE? I already had one and was
wondering if I should remove it. Hope you get this posting. Thanks again!

Did you try following the Overview link to
http://www.granite.ab.ca/access/splitapp/overview.htm ?

Mr. Steele,

[quoted text clipped - 15 lines]

front
end and back end? Please advise and thanks for your assistance!!

 

[Konchetta via AccessMonster.com]

Thanks Mr. Steele. Okay, I will have to make sure of the read, write and
execute on the back-end. I tried to open the FE database but my Main Form did
not open. I had to go to it to select it and I don't want them to have to do
that. Is there somethingelse I was suppose to do to allow for that form to
open as it did before splitting?

The location for the back-end sounds fine. Make sure that each user has a
minimum of Read, Write and eXecute on the folder where the back-end database
exists. For that matter, they should also have Delete (althought that's not
mandatory). This is the case even if you want them only to have read access
to the data: Access creates a locking file (.ldb or .laccdb) in the folder
where the database exists, and they need the ability to do that.

Passwords can be used if you want. To be honest, though, I've never worked
with passwords in Access, so I'm not sure whether anything needs changing to
accomodate them. If you're able to link the front-end to the back-end using
passwords, you'll probably be fine.

Hello Mr. Steele,

[quoted text clipped - 14 lines]