Forms on Back End?

[George-Bowyer]

If you are splitting an existing single-user DB into a multi-user FB/BE db, is it necessary to delete the forms, reports etc on the BE.

The only one I can think of would be to stop someone trying to use the BE directly by mistake, but file permissions should handle that.


Is there a downside to having forms etc remaining on a BE?


Many thanks,


George

 

[isladogs]

Why would you want to keep them on the BE?
It only takes a few seconds to delete them all

 

[theDBguy]

Hi George. The only form I may have in the BE is a big red warning form telling them to get out!

 

[George-Bowyer]

Why would you want to keep them on the BE?
It only takes a few seconds to delete them all

I guess I'm just I'm scared of deleting all my forms, queries and suchlike - it goes against the grain

 

[Frothingslosh]

You're not deleting them. You're moving them into the front end, that's all. Just keep a backup copy someplace, and update it as you update your app.

It's just as accurate to say you're deleting the tables and creating them in a new file as it is to say you're deleting the forms. The reality is you're just dividing the database into two different parts.

 

[Deleted member 147267]

file permissions should handle that.

How so, unless maybe you're talking about linking the be tables with a password?
You could consider having the db send you an email if it's opened directly, as long as you don't use a method that involves invoking an Outlook security warning to the user and you have a way of getting the information of that person.

 

[George-Bowyer]

All done.

Incidentally, the linked table manager spat out a table that contained a calculated field. When I deleted the relevant field (an old legacy - I don't use them any more) it went through fine.

Is that standard?