AccessDiscussion of Microsoft Access database design and programming. See also the forums for Access ASP and Access VBA.
Welcome to the p2p.wrox.com Forums.
You are currently viewing the Access section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
i am trying to set a user premission in access 2010 so the user cant mess with my design, just edit the data.... but i cant find that option... all i find is encrypt data base which it will set the whole database with a password...and i dont want it
You can then compile the frond end in the a .ACCDE. To lock it down even more you can rename the file from a .ACCDE to a .ACCDR
nice...
but i got question...
how do i retrieve the database from .ACCDE?
if i want to add more features and the client doesn't want to retype the data all over again....
how do i open his database from .ACCDE and edit it??
You do not edit the ACCDE. You compile the "master application " ACCDB into a new ACCDE. The data is all in the back end.
The data is store in the back end. The application or front end hold not data only the application objects. The front end is linked to back end.
I would suggest that you read the article I linked to plus all the other links at the bottom of that article. Then I would make a copy of your database and then split it. Do some experimenting on the copy that you split. Hopefully then things will start to make a whole to more sense.
hmmm
looks good but i read one of the ms office disadvantages
Microsoft Access MDE/ADE/ACCDE files
Databases that have had their source code removed (such as .mde, .ade, and .accde files) cannot be moved between 32-bit and 64-bit editions of Office 2010. Such databases that are created by using 32-bit Office (any version) can be used only with 32-bit Office, and a database that is created on 64-bit Office can be used only on 64-bit Office.
so what if my client has x64 office.... the .ACCDE .ACCDR. WONT WORK....
as for the ACCDE and ACCDB has to be togther in user pc which has no network connection between me and him???
if thats true then if i want to make any new change in ACCDB i have to get it from his hard drive?
hmmm
looks good but i read one of the ms office disadvantages
Microsoft Access MDE/ADE/ACCDE files
Databases that have had their source code removed (such as .mde, .ade, and .accde files) cannot be moved between 32-bit and 64-bit editions of Office 2010. Such databases that are created by using 32-bit Office (any version) can be used only with 32-bit Office, and a database that is created on 64-bit Office can be used only on 64-bit Office.
so what if my client has x64 office.... the .ACCDE .ACCDR. WONT WORK....
any suggestions?
The 64 bit version of Office is still really buggy and has lots of issues. At this time I will not support any clients that use the 64 bit versions.
I also thing of the 64 bit version just like having another version of Office. I have all the version of Office installed that I support. I create an MDE/ACCDE in every version of Access so that I can hmtach the version of Access installed.
as for the ACCDE and ACCDB has to be togther in user pc which has no network connection between me and him???
if thats true then if i want to make any new change in ACCDB i have to get it from his hard drive?
help plz
When you deploy a database, not just Access, you will have to create an update app that you send to the remote location that does the database updates. I have formation about this in the first link I gave you.
This is a common problem with deployed database applications. Even software like Quicken and Quickbooks have to deal with this issue.
IMHO, If the database is properly designed and normalized from the start you should not need to make many changes to the tables.