Front/back end...and...SQL?

[Toadums]

I hope this is the right spot >.< sorry if its not!

im having some trouble grasping the concepts of a front end/back end database...im relatively new to access, and have never even looked at SQL..so yah, lol.

So I have done searching on google/these forums for info...but I just cant seem to find anything that really helps me understand how to make a DB F/B end.

I think I have it right where like...you have a form that people can enter their data in, and they can see THEIR data...but they cant see everyone elses. and everyone elses data is stored in a big database of its own, with little off shoots of each individual person... (correct me if im wrong >.>)

So then another question...is this really a practical thing to do in Access? or is it something that is more reserved for like a webbased form that is filled out, then the info is stored in a big master database?

What I am doing for work is making a time sheet, my boss asked me to research front/back end DBs and try to incorporate that into the time sheet. His ideal is that it is all web based...I have already created the form that the people can fill out...its just the next step i dont know where to start...although for now it does NOT have to be web based, this is an ongoing project that I will just evolve

this post is kind of all over the place, sorry, im trying to say what i want the best i can, but ... think i am failing hehe..

if you have any information/tips on the topic, they would be GREAT to hear!! on anything ... concepts of F/B end, SQL, using the form i already have..and remember, im not really familiar with all the access/database lingo >.< (well, i kinda am i guess)

Thanks for any help!
Paul

 

[jsv2002]

Front and back end just refer to "splitting" the tables that contain the data from the rest of the database. There are several reasons for this a few being easier deploymet over networks (you give everyone a copy of the front end containing forms, reports etc..) and point their copy via linked table manager to the tables.

This can in some cases minimise corruption and allows for devlopement of the F/E without affecting the running of the live DB. Also it can cut down on network traffic as all the remote users are requesting is data from the tables they need access to at that time instead of just making a short cut to a remotely saved database.

As for SQL this is upscaling if you have more than say 50 users mainly for performance and the way it handles data more efficiently.

As for "web" interfaces" access don't really do that but 2007 has started making use of office live and sharepoint had a play with a small database myself using this feature but is in early stages yet.

As for people seeing "their" data and no one elses front/back end isn't designed to do that you need to look at your database structure maybe create logins and/or workgroups to restrict what people have access to....

good luck John

 

[Toadums]

As for people seeing "their" data and no one elses front/back end isn't designed to do that you need to look at your database structure maybe create logins and/or workgroups to restrict what people have access to....

Thanks John, this is really helpful...Now i know i dont really need to use SQL (only 9 of us in the Consulting company ) ...for some reason I had this impression that SQL was all online. See, since we don't have an office (we all work from home), It makes it harder..i think...to get the information back and forth. The way it is done right now is that a crappy excel spreadsheet is just emailed to the uh...person who deals with the money and my uncle (boss) just wanted me to try to make it go a bit easier...

So here is exactly what I am thinking...maybe front/back end isnt even the right term.

People fill out a form with 10 days from the two week pay period. then send it to the time keeper person, and then the data is plopped into a big master database that holds all the time records...like each 2 weeks you just add the information from the table populated by the forms from each employee to the master database...then the time keeper can query by name or what ever...eventually, however, it would be nice to make it web based.

Your post made me realize...sharepoint. i completely forgot about sharepoint...i used to use it...although never with access. perhaps i will check out the compatibility...

I will check with my uncle to see if there are any 'confidentiallity' issues...I cant see the harm in people being able to see how long other people work...save having to worry bout logging in and such...which could be fun (i like vb hehe)

Thanks again,
Paul