470,636 Members | 1,601 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 470,636 developers. It's quick & easy.

MDW and runtime access

12
I am hoping somebody can help me with this small problem, I have created a workgroup file and it works fine with people who have the full version of access 2002 i.e it prompts them to enter username and password, however, some people have Runtime Access 2002, when they open the database it does not prompt them for any user details, is there a way geeting those who use runtime to prompt them for user details.

Any help on this will be much appreciated.
Oct 26 '06 #1
7 2895
NeoPa
32,301 Expert Mod 16PB
Have you run 'Workgroup Administrator' on their PCs and set it to your .Mdw file?
Oct 26 '06 #2
ditch
12
There is 10500 machines and they all have runtime access on, are you suggesting that I would have to run this on every machine.
Oct 26 '06 #3
NeoPa
32,301 Expert Mod 16PB
No, if you have that many PCs then you'd probably use a multiple Registry updater of some form (SMS; Scripting; etc}.
If you have that much resource you should have someone there who can set that up for you.
Oct 26 '06 #4
ditch
12
Thank you for helping me, however, I have been a bit of a dumbass I forgot to include in the path the location of the msaccess.exe file, what a silly man I am
Oct 27 '06 #5
PEB
1,418 Expert 1GB
Ammmmazing! Really amazing!!!

For the first time in my short live I've heart that Access is installed on a such number of machines!

And all are connected to 1 mdw???? How Access suports them??? It's very curious for me?

The Access specifications are for 255 concurent users my God!!!

And here 10500! Access will beat MS SQL SERVER!!!

There is 10500 machines and they all have runtime access on, are you suggesting that I would have to run this on every machine.
Oct 27 '06 #6
ditch
12
The reason they all have runtime access is they hotdesk and the majority of users have links to various databases, so it just made sense to install the runtime on all machine, saves a lot of resouce.

The organistaion has some 5000 database's in one form or another, it's starting to become a nightmare moving these either to a unix or ms sql backend.
Oct 31 '06 #7
NeoPa
32,301 Expert Mod 16PB
Basically, the way the MDW security has been implemented in MS Access is piss-poor.

When I had a similar problem (nowhere near as many as 4,000PCs just lazy really) I set up a Reg file which is more easily applied.
The contents were :-
Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\8.0\A ccess\Jet\3.5\Engines]

"SystemDB"="G:\\Database\\STPSecurity.Mdw"

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Office\9.0\A ccess\Jet\4.0\Engines]

"SystemDB"="G:\\Database\\STPSecurity.Mdw"
which, you'll notice covers two versions - 2K & 97.
The file was created using RegEdit.Exe (all the usual warnings etc.), after I'd set up my PC with the correct settings.
From the 'Registry' menu select 'Export Registry File...' making sure 'Export Range' is set to 'Selected Branch'.

Obviously, the key used for later versions of Access is likely to be different, but only in the version number bits I would guess.

To apply the Reg file, simply Open it from Windows Explorer or type it in the 'Run' box.
Oct 31 '06 #8

Post your reply

Sign in to post your reply or Sign up for a free account.

Similar topics

1 post views Thread by B&C | last post: by
9 posts views Thread by Charisma | last post: by
9 posts views Thread by Paul H | last post: by
6 posts views Thread by SMcK | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.