I have designed a database for a group in my organisation, which I have been happy to do, but it is my first attempt at anything so sophisticated.

I feel like I am trying to run before I can walk, having been enticed by what looks like a 'neat' way of doing things.

We are in a network environment, other databases in the organisation are ms2000 and have lots of vb code, so I can't really use them too closely as sources of inspiration as I have already made use of some 2007 features.

I am using forms and subforms to enter and read data into a dozen or so one-to-many related tables - I have got the hang of using tables to provide editable combo boxes for entering data into several tables.

Currently only 2 people will be using the database, but there is a good chance they will want to be using it at the same time.

I made a front end saved on the local client computer, linked the tables to the accdb format database tables on a file server.

I have read that using forms based on queries can reduce network load as only the queried info is transported back and forth across the network.

Have also experimented with saving a frontend in accde format which is lots smaller than a linked accdb one - problem I have is the forms aren't editable. I've read this may be because they aren't "unbound". The entries in the table can be scrolled through using the navigation bar buttons, but I can't add data.

I'm basically trying to assess what is my best approach here - whether to completely redesign all forms, or just create some new ones for entering data. Do I need to design some append or update queries, then make forms based on these queries? Will these work when the front end is relinked to tables in back end and it is saved as accde?

Many thanks for any assistance.
A

We are in a network environment, other databases in the organisation are ms2000 and have lots of vb code, so I can't really use them too closely as sources of inspiration as I have already made use of some 2007 features.


I am not sure why you think you can not use the 2000 database as sources of inspiration. I can not think of anything that would be done in the 2000 databases that you can not use in 2007. You just can use 2007 feature in 2000.

I would urge you to look at All the old Access 200 to 2003 database you can to learn about stuff you can use ion 2007. I think the reason why you do not see lots of 2007 specific example is because you can use anything from pre3vious versions. I do not convert my example to 2007. I keep them in 2000 format so it will work with more version of Access.


Have also experimented with saving a frontend in accde format which is lots smaller than a linked accdb one - problem I have is the forms aren't editable. I've read this may be because they aren't "unbound". The entries in the table can be scrolled through using the navigation bar buttons, but I can't add data.


I only deploy split applications with a MDE/ACCDE front end. The forms do not become unbound in an ACCDE. If you are not able to do data entry intot he forms, then you probably have tust center/file permission issues.

The user must have read and write permissions for the folder where the back end is located.


I'm basically trying to assess what is my best approach here - whether to completely redesign all forms, or just create some new ones for entering data. Do I need to design some append or update queries, then make forms based on these queries? Will these work when the front end is relinked to tables in back end and it is saved as accde?


Splitting your database and using a ACCDE should not cause you to redesign your forms.

I would wait until you learn more about using a front end as a ACCDE and a back end on a "serve"r before you think you need to redesign your forms.

Thanks for the help. I'll look at the trust/file folder permissions. With hindsight that could be an issue as I'm not sure the 2nd machine I was trying out the front end on has write access to that network folder...

In the meantime I have been working on the backend as a standalone. There are only a dozen or so tables but the whole database bloated out to over 109mb in size.. I ran repair and it came down to just over 1mb. .. I'll be back!

The front end will bloat a lot when you are editing objects. That is why I crete an MDE/ACCDE when I am rady to deoply. This compacts the databse and since you can not edit most objects, it helps keep the bloat down.