splitting the database

[AccessWillKill]

Hello,

my current place of occupation is wanting to split their current databases so there is a front and back end. Now obviously there are much better ways of doing this as i know. but the company is wanting to stick with access (presumably for financial reasons)

we have successfully managed to split a database however for some reason our switchboard fails. We believe it is something to do with security settings been too high on the database.

Is it possible to reduce these at all?

 

[RuralGuy]

I would keep the SwitchBoard table in the FrontEnd if it is SwitchBoard created using the SwitchBoard wizard.

 

[AccessWillKill]

i dunno how it was created. i didn't create the switchboards personally. Theres just something stopping you from splitting the database because of it.

is there away to change the access security settings. like they have with macros

 

[RuralGuy]

Move the SwitchBoard table back into the FrontEnd. What version of Access are you using?

 

[DCrake]

You don't have to use the database splitter to split the database.

1 Create a blank database and name it accordingly AppData.Mdb
2 Import the tables only from your original application
3 Open your original database and delete all the tables***
4 use the link table manager/import to link to the newly created appData.mdb


***Don't forget to make backups before you start.

 

[RuralGuy]

David: I still think the SwitchBoard table needs to be in the FrontEnd.

 

[DCrake]

Yes I agree I was just trying to explain the manual method of splitting a db.

 

[AccessWillKill]

i've been given an update on this from my manager, which is where the confusion has come from.

Apparently (the database is currently working in 2003)

he wants to split the database but also split the version of Access. So he is wanting the back end of the database to be Access 2010, While the front end is in Access 2003 or Visa Versa.

would the manual way for this work, would it work at all (given theres different file extensions), or is there a different way of doing this?

 

[RuralGuy]

Access 2010 can use an Access 2003 mdb but Access 2003 can *not* read an accdb file.

 

[gemma-the-husky]

as alan says its a backward compatibility issue

the data tables need to be at the lowest version of any of the front ends

so eg, if you have any A97 users, the back end would need to be A97.

so you can't have a backend in A2010 - why would you want to anyway - why is it important for the backend to be a particular format.

 

[AccessWillKill]

i'm not completely sure why to be honest. i think its to do with lisencing and saving cash or something. i just get given information that is deemed as 'needing to know' Which is apparently not alot.

so are you saying its not backward compatible IE you can't use 2003 front end with a 2010 back end or not backward compatible IE you just simply can't do this at all.

i didn't think it would work myself, but as long as i have evidence of this it'd put my point accross better

 

[DCrake]

Take a look at this Link.

 

[Galaxiom]

I can't see how licencing would be an issue. The backend is simply a file share. The server doesn't need a licence to store that file.

As others have said, the front end can only read files that it understands so an Access 2003 front end cannot read an accdb file. Also note that there are features in the A2010 accdb that cannot be used by A2007.

Best stick to mdb on both backends and front ends.

Access 2007 Runtime can run mdb or mde frontends quite happily.

 

[boblarson]

And if you think of it this way - Access 2003 was released many years before Access 2007 or 2010 was released. So, how would there be a way for it to use a later version as a backend because it has no concept of something that was designed and developed way after it was. However you can use a later version frontend and an earlier version backend just like Galaxiom, Dave, and Allan have said.

 

[AccessWillKill]

right. we've moved to a different direction. The database is being ran across access 2010 solely but the problem now is unsafe expressions when its split.

how do you reduce macro security on the front end. You know like on the clients PC's. like when its all on a single users PC's you can switch them off in the settings. but the settings won't be there on users pc's when its being ran as an application

 

[boblarson]

right. we've moved to a different direction. The database is being ran across access 2010 solely but the problem now is unsafe expressions when its split.

how do you reduce macro security on the front end. You know like on the clients PC's. like when its all on a single users PC's you can switch them off in the settings. but the settings won't be there on users pc's when its being ran as an application

Each computer has to set up a trusted location or make the database a trusted document. To set a trusted location you can do this (this is for Access 2007 but it is similar except that instead of the round office button you have the menu item FILE to select)