unable to edit accde version of split databae

[blueman]

Weird problem:

I have a split database that I created for my business. I gave a .accde front end version to my partner. Though he is able to enter new data, he can't change existing data in his front end. I went to his PC and tested his back end and was able to edit/change data in the tables but in the front end in forms, I could not. I obviously couldn't see any property settings for those forms as he had an accde version. I did go to my front end version and it works fine. The only thing I did was to create an accde version which I gave to him. I checked my front end to make sure I allowed edits in the forms that had been having these problems and they were all set to allow edits.



Further, I took his front end and back end and brought it back to my pc and linked everything up again. It works fine.

Help would be appreciated. Thanks

[June7]

Why bother with accde? He can't hurt your master copy and so what if he blows up his copy? Is there a concern he will go directly to objects in navigation pane?

What do you mean by 'his' backend? Aren't you both working with the same backend?

[ItsMe]

...create an accde version which I gave to him...

To add to June's comments, what version of Access did you use to create the accde and what version of Access was used to open/run it?

[blueman]

They're both access 2007.

The accde was there just as further protection. He didn't want to be able to see or mess with any of the underlying mechanics and I didn't want him to, so I obliged. And what would be the downside with using accde? I've done it before without problems.

The backend could belong and be used by both of us and probably will be at some point. Currently he's using it himself on his computer.

Still: why is this happening?

[June7]

I've never distributed accde. I use project settings and code that disable ribbon and shortcut menus and hide the navigation pane. But when I open the frontend I hold down shift key to override so I get everything.

If he uses own backend and you use your own backend, that is two data files. Don't need all data in one file?

I don't know why he has issue with viewing data he has input. Certainly can't see data in your backend unless there are links set to that file.

[blueman]

That's what accde's are supposed to be for I thought. I don't use the back end as of now, so there's no duplication of data with 2 back ends. It's not viewing the data that's a problem, it's editing or changing the data that is not being allowed.

[ItsMe]

...it's editing or changing the data that is not being allowed.....

It could be a permissions issues. However, I would expect the DB to, simply, not work. IIRC, in order for the accde file to retrieve data, it needs to have write permissions at the folder where the BE resides. There could possibly be an issue with the security settings of the BE file, itself. If you created the BE file on your computer and then copied it onto another computer using a different user profile, the owner of the file is the User Profile that copied it over. There are advanced settings under the security tab to change Owner of child objects within a directory.

[pbaldy]

I usually distribute accde's, so that isn't likely the problem. If it was a permissions problem, I wouldn't expect him to be able to add new records either. You might try the accdb on his PC and see if it works. I'd be surprised if it did, but it wouldn't be the first time I was surprised.

[blueman]

There could possibly be an issue with the security settings of the BE file, itself. ...

The BE on his PC works fine. I went in directly to the tables and was able to edit data. However, when I go into his FE and view an existing record in a form, I'm unable to change the data.

[ItsMe]

There could be properties within the FE that would cause this symptom. However, when comparing the accdb FE file to this accde file, there should not be any difference. Like Paul mentioned, if you do a side by side test with a copy of the accdb file, they should behave the same. Without the side by side, we will continue to guess. If the side by side comparison has been done to your satisfaction, create another accde file.

At least that would create a benchmark.

[blueman]

There could be properties within the FE that would cause this symptom. However, when comparing the accdb FE file to this accde file, there should not be any difference. Like Paul mentioned, if you do a side by side test with a copy of the accdb file, they should behave the same. Without the side by side, we will continue to guess. If the side by side comparison has been done to your satisfaction, create another accde file.

At least that would create a benchmark.

Thanks,
I'll try a side by side on his computer tomorrow and report back. This behavior did occur in the new instance of an accde file that I created from my accdb as well as in a previous version.

[blueman]

Interesting:


So I tried my ACCDB on his PC before doing anything else - It worked fine. I could edit data in forms without a problem.


I converted the ACCDB to an ACCDE and it worked fine. I could edit data in forms without a problem. I did notice there was a lock on the file icon and didn't know if that was normal or not so I took a screen shot. Nevertheless, lock and all, it worked.


The last thing I did was to get rid of the navigation pane so he wouldn't be messing with anything he shouldn't mess with. I decided to check it again and low and behold: can't edit form data. There doesn't seem to be anything associated with edit-ability with that navigation check box. I have no idea why this would be happening. Hopefully, someone does.


Thanks

[pbaldy]

The lock icon is normal; mine all have it. I always uncheck that box so the nav pane isn't displayed, don't generally set anything in the nav options area. You're saying unchecking that box makes the user unable to edit existing data, but they can still add new data? And if you leave it checked, they can edit? That's really weird. I suppose you can try leaving it checked but having code in the startup form to hide it. You can also look into giving him an accdr, which forces him into runtime mode. I've never done it that way, but I do force most users into runtime mode with my version control utility (using the command line switch).

[ItsMe]

... don't generally set anything in the nav options area....

I don't play around with the Navigation Options either. I just uncheck the box and hide the whole thing. I was going to ask how you were hiding the Nav Pane. Seems like goofing around with the options may be the culprit. As for the lock icon for the accde file, it has never been a concern to me. I always expect it to be there in accde files.

[blueman]

Nothing was changed, to my knowledge in the navigation options. I only opened it to show what was in there in case it was helpful. The only thing I did was to unchechk "show navigation"