Difference: Split database and make Accde

[jumbledore]

What's the difference between "Split database" and "make Accde"?

 

[jumbledore]

More or less, that's the gist.

When you split the original database, the resulting "original" piece just has the data tables in it, while the new Front-End has all the other objects and links to the tables in the original.

You only distribute the accde to to users. You don't actively use the non-accde copy of the Front-End for anything. You just need to hold on to it in case you want to make any changes to the Front-End (in which case you would do it there, and then create a new accde from that).

Hi Joe, thanks for all your help. I have just one more question. What happens when you keep the "original" database with only the tables on a network folder, which has restricted permissions and you provide the copies of the front end to users who may or may not have permissions to that folder?

 

[Joe4]

If you want users to be able to use the database, they will need the appropriate permissions to the location where those tables reside.
So either you will need to give them the appropriate permissions, or put the database somewhere that they have access to.

 

[jumbledore]

Thanks. I just split my "original" database and put the split db with only the tables in a network folder. I then created a "front end" which resides on my desktop. The front end includes a form from the "original" db which allowed users to enter some values via text boxes. But when I open this form through the front end the textboxes appear to be disabled. Why is it so?

 

[Joe4]

Are macros/VBA enabled for that user?

 

[jumbledore]

Are macros/VBA enabled for that user?

Yes macros are enabled. The user is me. I am testing the front end. I have created another form in the same database which allows me to view the records in the table but the form which should allow me to update the records doesn't display the textboxes

 

[Joe4]

Not sure. Without access to your databases and network environment, I am afraid there is not much I can do.
My only thought is perhaps that front-end copy is corrupt, and you may want to try creating a new one and see if it has the same issues.

 

[jumbledore]

Not sure. Without access to your databases and network environment, I am afraid there is not much I can do.
My only thought is perhaps that front-end copy is corrupt, and you may want to try creating a new one and see if it has the same issues.

I tried creating a new front end but it's still the same issue. I followed the instructions from here: https://support.microsoft.com/en-us/kb/304932

The back-end database is saved on a network drive with full read write access and the front end is on my local drive

 

[Joe4]

I wouldn't think that the back-end has anything to do with why Text Boxes wouldn't be visible on your front-end.

 

[jumbledore]

I wouldn't think that the back-end has anything to do with why Text Boxes wouldn't be visible on your front-end.

I realized what the problem is. I had not given myself full control of that folder. I have updated the permissions and have fixed the problem. But thanks for following up.

 

[jumbledore]

I wouldn't think that the back-end has anything to do with why Text Boxes wouldn't be visible on your front-end.

Hi Joe,

I have one more question. Now the db that I have created stores the paths of some docs on a shared drive. And these are presented to the user through forms. So if a user wants to access these docs he has to click the link which opens that particular doc. The problem is the links that the user clicks on shows the entire path of the file. And since I have to give full rights to the users to make the forms work it's possible they could locate the folder through the file paths and play a mischief with the files on the shared drive. So how do I prevent Access from displaying the paths while at the same time provide a link to the users to click on?