Local FE for each user - a discussion

[jonathanchye]

Hi all,

Just want to know opinions on this matter. Previously I have my FE sitting on a network share and users create a shortcut to this file. This has the following benefits :

• Small filesize/footprint on user PC
• Customisable icons P)
• Possibility of just having one shortcut for all databases thus reducing clutter

However, I find this to be a major problem if I were to carry out an update on the FE. We don't have a lot of users (around 80-100) but still enough to cause problems


What I did next was just to have the users copy the source file onto their desktop. So when I apply the update I just overwrite the source file, trigger the version checker and each users' local FE will update automatically next time they log in. Although slightly high maintenance this works brilliantly at the moment for me.



However, the more databases I build they more files users will have on their desktop. I can't customise icons so each file looks the same and some users do complain. Desktop (roaming profile) filesize also bloats as some clients are 30MB in size. Updates works a treat but obviously that came with a price.


What would be ideal in my situation is to just have one shortcut on each user desktop. This shortcut will open up a "switchboard" or gateway database which users can then select which one to log onto. However, I can't see a good way to implement whilst still having a local copy active...


What do you guys think is the best idea for improvment? Is it advisable to stick to what I have now?

 

[gemma-the-husky]

I think the main thing is that most of us would try and ensure that multiple users do not share the same copy simultaneously.

i actually put code in my network masters to prevent them being run (eg if the drive letter is above H:\ which caters for most situations

multiple users sharing the same database is may be ok, but one issue is that if you write stuff to local tables, or maybe the registry, then users start to interfere with each other.

 

[jonathanchye]

I think the main thing is that most of us would try and ensure that multiple users do not share the same copy simultaneously.

i actually put code in my network masters to prevent them being run (eg if the drive letter is above H:\ which caters for most situations

multiple users sharing the same database is may be ok, but one issue is that if you write stuff to local tables, or maybe the registry, then users start to interfere with each other.

Yes, that is my concern too. I still have stubborn users who create shortcuts to the source file but I've created a code to check for that and terminates the program if it's run from source

I'm just wondering if there's any elegant solution where users won't need to have 5-6 accde files on their desktop and also a way for me to customise icons so the databases look different

 

[VilaRestal]

Definitely keep the FEs on the local HD. You can assign them icons in the Access Options - Current Database.

(I think PixelFormer is a good freeware icon editor)

Put all the icons on the local HD too in a standardised location and set the FE's icon from the local icon file (on a computer that has the icons.

Then you wouldn't necessarily need a dashboard.

But building a front end dashboard - each button opens a different database - wouldn't be hard to do either.

 

[jonathanchye]

Ah yes, I've done this but the "icons" only appear on top of forms etc. What I am on about is the actual icon you click on to start the database. AFAIK it's not possible to do this unless you use the shortcut method?

Definitely keep the FEs on the local HD. You can assign them icons in the Access Options - Current Database.

(I think PixelFormer is a good freeware icon editor)

Put all the icons on the local HD too in a standardised location and set the FE's icon from the local icon file (on a computer that has the icons.

Then you wouldn't necessarily need a dashboard.

But building a front end dashboard - each button opens a different database - wouldn't be hard to do either.

 

[KenHigg]

For what it's worth, here is how I would do it:

http://www.access-programmers.co.uk/forums/showpost.php?p=663369&postcount=16

 

[VilaRestal]

Ah yes, my mistake. I'm so used to packaging front ends I take for granted that their shortcuts don't automatically get their icon from the database.

Having the shortcuts on the desktop with their own icons is not a problem though. (Again, so long as all the icons are in a standardised location on each local HD.)

Putting the FEs themselves on the desktops is not ideal: too easy for a user to delete them.

 

[RainLover]

For what it's worth, here is how I would do it:

http://www.access-programmers.co.uk/...9&postcount=16
__________________

ken

Looks like the way to go.

I do something similar but use VBS.

Same result.

There is a problem with users in that they like to play with things they shouldn't.

I have always found that a big gun usually solves this problem.

 

[Lightwave]

You seem to have plenty of information on icons - but seeing as you are looking at polishing things up here's something you can do with splash screens.

With access you can replace the Microsoft splash screen with your own version.

Create your desired splash (I like to use Inkscape this can be used for icons as well very good opensource vector graphics package) and save it as a bitmap.

Place said bitmap in the same location as your front end with EXACTLY the same name (apart from extension) as the accde. When the front end loads up the usual Microsoft flash is replaced by your choice.

Note on fast machines the splash sometimes gets loaded and unloaded so quickly you don't see it...

 

[jonathanchye]

For what it's worth, here is how I would do it:

http://www.access-programmers.co.uk/forums/showpost.php?p=663369&postcount=16

This is almost what I have now but mine is much simpler. I just have a tickbox on the "master FE" that marks it as the Master copy so updates will skip running if this tick box is checked. This prevents situations of infinite update loops

Thanks for the link though I will definitely have a good read to see how I could further improve.