LinkBack URL
About LinkBacks
I want to work on a excel file with access as backend.
I want to delete update next previous, all the functions on the excel file with back end as access from where should i start.
THANKS,
Deepak
I want to work on a excel file with access as backend.
I want to delete update next previous, all the functions on the excel file with back end as access from where should i start.
THANKS,
Deepak
Is there no body to help me guide me some tutorial then
Regards,
Deepak
There's an example here (http://www.excelforum.com/tips-and-t...ql-server.html) for using a MSSQL back-end - the principles are identical. I have to ask though, why not just do it all in Access? People don't need access installed to use the application, only the free run-time
Can you please educate me to know how this can be done?Originally Posted by Kyle123
Wanted to learn this stuff because in my work place I am the only person having the Ms-Access and due to license issue I cannot able to develop more database in access and give it to all because Tech person not giving Ms-Access to everyone.
It will be very much helpful to me if you share some thing on this
If your problem is solved, then please mark the thread as SOLVED>>Above your first post>>Thread Tools>>
Mark your thread as Solved
If the suggestion helps you, then Click *below to Add Reputation
You split the database, so you have a front-end and back-end. Users only need a copy of the front-end to use the application and it doesn't require access to open - you only need the access runtime, which can be downloaded freely here: http://www.microsoft.com/en-gb/downl....aspx?id=10910 (there are versions for other versions of Access)
Thanks for the info and link
I request your inputs on my below doubts.
1) After splitting the database, is it possible to change the design in table, form, report, adding/deleting queries? it will get reflected to the users?
2) When the users are working with the database whether the admin can change the disign in the front end?
3) Whether User Level Security can be applied and split can be done?
4) Compact and repair can be done from the front or back end?
These are all the immediate questions which came to my mind after seeing your reply.
Forgive me for asking, but isn't hijacking another forum member's thread breaking rule #2?
Ali
Enthusiastic self-taught user of MS Excel who's always learning!
Don't forget to say "thank you" in your thread to anyone who has offered you help.
You can reward them by clicking on * Add Reputation below their user name on the left, if you wish.
Forum Rules (updated August 2023): please read them here.
Access Databases should be split anyway, I don't use access (for a variety of reasons) so my answers may not all be up to date, but I'll answer as best I can:
1. Look up the concept of a split database, some of the items you've listed are in the front-end, some are in the back-end. The front-end is essentially a client, so they contain the UI, forms etc and they connect to a singular back-end which contains our database.
2. Yes, but the front-end will need redistributing, just like any other software application - there are tools to make re-distribution of the front-ends easierThe contents of the back end is made up of Access tables only. These hold the primary data stored within the database.
The front end is comprised of all the Access queries, forms, reports, macros and modules. It is the user's means of operating the database.
The front end has links to the back end so that the front end can access the back-end data store. The front end file contains the user interface, through which users input, edit, view and report on the data.
One reason for constructing an Access database out of a front end and a back end is to provide for simultaneous use of the database by more than one person. In this multi-user form of the database the back end normally resides on a network server, and each user has a front end on their computer.
3. Pass, I haven't used Access for a long time, so I suspect that any advice I give here would be innaccurate
4. Compact and repair would be done within access, not the front-end.
Really not a hijack since my question is entirely relevant to the answer provided by Kyle to the OP in Post #3Forgive me for asking, but isn't hijacking another forum member's thread breaking rule #2?
Hi Kyle123,
Thanks a lot for the kindness in explaining it briefly
I will give a try now...
There are currently 1 users browsing this thread. (0 members and 1 guests)
Posting Permissions
Register To Reply
Bookmarks