Newby Split database questions 1

[ribhead]

Howdy I have some basic questions on a split database. I have created a project in which up to 10 people will be entering data at the same time. So, I've read that it's a good idea to split my database. I did this and I believe it was successful however I have some questions.

P.S. I have the file on a Network vs on the hard drive.

1. What are the negatives about splitting a dbase?

2. After I split the dbase do I need to do anything special to the front end tables?

3. Should the tables on the front end fill up as the users are entering data?

I know these probably seem like dumb questions but I don't have anyone around my work to answer them.

Thanks.


Thanks, Rib

Bartender:Hey aren't you that rope I threw out an hour ago?

Rope:No, I'm a frayed knot.

 

[GingerR]

1. I haven't found anything negative. it's the best way to go. you can change form/report/front-end programming in a DEV copy of the front-end then just overwrite the front-end and it doesn't affect the data. except if you have the tables in the front end...

2. why do you have tables in the front end? the tables should be in the back-end, and forms/reports in the back-end.

3. see #2 above.

one thing is to periodically compact the back end. maybe that's what you mean by "will the tables fill up". Yes they will.

 

[ribhead]

Ginger

Thanks for the response.

I have tables in the front end with a black arrow icon next to them. I used the Database splitter Wizard. Perhaps I did it wrong?

Thanks, Rib

Bartender:Hey aren't you that rope I threw out an hour ago?

Rope:No, I'm a frayed knot.

 

[Chance1234]

The tables you see in the front end with teh arrows are just a visual way of access showing you the tables are linked. When you open up a table in the front end you are in fact opening the table in the backend.

When the user enters into your forms in the front end. The data is passed to your tables in the backend.




Chance,

Filmmaker, gentlemen and forum1229

 

[SimonDavis]

Only problem I ever had was that the backend resided on a server, the front end locally (some people had slightly different versions, depending on what they need access to), so I'd access the backend via a shared drive.

This meant that all users had to have the share mapped on their workstation the same - in this case drive G:

The front end would reference the tables through this drive, so if it wasn't mapped, the front end couln't find the back end. Occasionally that drive letter was already mapped when I came to install the database, causing more fun . . .!

I guess someone will now tell me I did it all wrong. At the time I think it was the only way to do it, but I did start development 5 year ago!

 

[Chance1234]

As your a newbie ribhead, you might want to condsider the following to make sure your users have the right version of the front end. faq181-5559



Chance,

Filmmaker, gentlemen and forum1229

 

[GingerR]

SimonDavis--you can avoid all of that. When you're using the Linked Table manager, manually type in the full path instead of just browsing and using the drive letter:

\\servername\sharename\path\DB.mdb

Actually if you just type in the servername+sharename, that's enough and then you can browse the rest of the way if you want. It'll build the path for you.

this way no one has to map anything.

g

 

[SimonDavis]

Thanks Ginger - I suspected that was the case, but at the time I'm not sure why I did it, but I seem to remember a problem - maybe as simple as me typing the servername wrong, and deciding the easiest way was through the share. Also this was access 97, maybe it was that.

Anyway, much too late now! Thanks for the tip though.

 

[ribhead]

Hello Everyone,

Looks like there's some good discussion about this topic but I want to make sure I'm understanding the very basic structure. I will have a backend located on a networked server, and a Front end with forms,queries,modules,etc..? Do I also have the linked tables in the front end? The ones with the black arrows or do those go in another file on the server? Again not looking to be overwhelmed just basic unga bunga language for my dinasour brain.

Thanks, Rib

Bartender:Hey aren't you that rope I threw out an hour ago?

Rope:No, I'm a frayed knot.

 

[GingerR]

Yes the front-end contains links to the tables in the back-end which is on a server. Each user may either have the front-end copied to their hard drive, or you can put the front-end on the server too and simply supply each user with a shortcut to it. Also in your front-end are the forms, reports, queries and such. The back end contains just the data tables. Do you see it now? Do you see why?

Say you have everything in one database and the users are using it. You have a development copy that you make some changes to some reports. Since you cannot just replace the Production database with the development database (because the data in the tables is outdated in the Dev version) you'd come on this forum and ask how to get the changed reports into the Production database without messing up the data, and someone would suggest to you that you split the db )

By the way, you can see all of your linked table details by choosing Tools + Database Utilities + Linked Table Manager from the menu.

So, in regards to your orig post, you don't really have to do anything if it's split and people are using it and it's working properly.

 

[ribhead]

Thanks GingeR this is exactly the info I am looking for. I do see the importance of splitting and why it's done. I'm just not sure if I want to put the Font end on the Network or on the HD. I'm lazy and not all that sharp so perhaps the network is my game here.

By the way thanks for the help. Have a star on me.

Thanks, Rib

Bartender:Hey aren't you that rope I threw out an hour ago?

Rope:No, I'm a frayed knot.