Spliting database

[officemanager2]

Hello: Followed all the insturction from the Access 2010 Missing Manual, as well found similar instructions on line but when I split the database into front and back end the front end still contains all the table information when I transfer that file to a different computer.

Any suggestions?

 

[Hap007]

The frontend should still contain all the table information.

Before the Split, the access file included all Forms, VBA code, Reports, Queries and tables.

After the split, the BackEnd should now have all the Tables and the FrontEnd should contain links to those tables along with the code etc..

After you completed the split, did you open up the 'New' Frontend?

Hap...

Access Developer

http://www.fcs-software.com/fcsaccessdev.html

Access based Accounting Solutions - with free source code
Access Consultants forum

http://www.tek-tips.com/threadminder.cfm?pid=1121

 

[MajP]

Any chance your tables have a little arrow by them?

 

[officemanager2]

Hello MajP & Hap007: You two help me a lot so thank you for that.

I guess my confusion is that I thought on the 'new' frontend(s) the end user would not have direct access to the tables.

I've created the front ends with the file extension .accdb to prevent the forms from being modified, but there is still full access to the back end of the database.

I understoond with the split that the end user would still be able to input data through the forms but they would not have direct access to the tables and not have the ability to open and alter them.

My concern is some of the end users have no idea how access, and most programs work, but I'm always amazed at how 'deep' they get into the computers and create problems. I've set up the database to open with the switchboard taking up the full screen, but end users still get into areas they shouldn't and make a mess of things.

Anyway thanks for the feedback, and if there is a way to create access only through the forms please let me know.

thanks again.

 

[MajP]

There are a lot of things to keep people out. Especially if they are not actively trying to "break-in"

1)You can hide the tables
2)You can hide the navigation pane
3)you can control everything through pop up forms.
4) You can control the menus.
Prior to Access 2007 you can use User Level security.

 

[officemanager2]

Sounds good. I figured I could hide the navigation page but I haven't figure out how to yet. Hiding tables is new to me though.

I believe the VB code is protected when the DB is saved as .accdb .

The last two are new ideas to me, if you have any good links please post them if you have the time.

thanks

 

[MajP]

Things are different with hiding the navigation window and menus with 2007 and beyond. So some of these are no longer valid

http://blogs.techrepublic.com.com/10things/?p=552

look at the start up options for menus and navigation pane.
Working with ribbons is a little more involved then old menus. You will need to google.

http://www.accessribbon.de/en/index.php?Access_-_Ribbons

But once I hide the nav pane and ribbons, I do everything with pop up modal forms. So the user only gets the features that are provided by the form. So the db opens with a menu and then from there you can only go from form to form. Doing this you need to consider what menu choices you have taken away from the users. In general all forms have buttons
ok
cancel
close
return to main menu
And likely
add
delete
sort
filter

If you have a way to get feedback from the users this is OK. Because if they are used to doing some menu choice that they no longer can get to then you can add in features and shortcut menus of your choice.