Multiuser:

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am designing an ms access application that many users will be using. Due
to the number of people, I would rather not use the distributed front end
application re: changes and re-distribution..yadda yadda yadda.

Can forms be opened and used simutaneously by users using data unique to the
user? I hope this isnt too vague, but the I have a distributed fromt end
database application and everytime we make a change to the front end, we must
re-distribute the front end to about 25 people...inexperienced users get
confused and generally..people are not happy with this solution...even though
i dont have a problem with it!

Any suggestions?? I will entertin any and all at this point!

Best regards
Kevin
 
Dear Kevin:

You can create an automated process that is transparent to the users. Take a
look at Tony Toew's AutoFE Updater.

http://www.granite.ab.ca/access/autofe.htm

Roger Carlson also has two sample databases that deal with this issue; look
for files named "KeepingDatabasesInSync..." at

http://rogersaccesslibrary.com/TableOfContents3.asp

There may be other possible solutions available. I've only had experience
using the AutoFE Updater.

Good Luck!
Fred Boer
 
faberk said:
I am designing an ms access application that many users will be using. Due
to the number of people, I would rather not use the distributed front end
application re: changes and re-distribution..yadda yadda yadda.

Can forms be opened and used simutaneously by users using data unique to the
user? I hope this isnt too vague, but the I have a distributed fromt end
database application and everytime we make a change to the front end, we must
re-distribute the front end to about 25 people...inexperienced users get
confused and generally..people are not happy with this solution...even though
i dont have a problem with it!
Click to expand...


There are many, many issues related to sharing a front end.
Your troubles with distribution need to be addressed with
out trading them in for an even more severe set of problems.

I strongly suggest that you take a look at using:
http://www.granite.ab.ca/access/autofe.htm
 
I've only got a 5 user system, and I don't require anything beyond a singe FE
..mdb file. However, I've had the best success simply writing a VBS script
that copies the FE from a shared resource onto each user's desktop. Whenever
I make an update, I just create a new FE and save it in that shared drive,
then tell my users to run the VBS file.

I can post the code for that if you like.
 
Code...yes, if you dont mind please!

MDW said:
I've only got a 5 user system, and I don't require anything beyond a singe FE
.mdb file. However, I've had the best success simply writing a VBS script
that copies the FE from a shared resource onto each user's desktop. Whenever
I make an update, I just create a new FE and save it in that shared drive,
then tell my users to run the VBS file.

I can post the code for that if you like.
Click to expand...
 
The VBA file is esident on each user's desktop. Everyone using it has Windows
XP, though it should work in Win@k or even Win98SE. The code puts the FE
right on the users' desktop, simply overwriting the current one. All five of
my colleagues sit within walking distance, so I didn't really bother to add
error-checking code. If you're in a truly remote situation, I might suggest
adding some error checking to ensure that the copy is successful, etc.

HTH

DBUpdate.VBS
==============================================

Option Explicit

Dim objFSO, objShell

Dim strSource, strDesktop

strSource = "S:\<path>\Disputes.mdb"

Set objFSO = CreateObject("Scripting.FileSystemObject")

Set objShell = CreateObject("WScript.Shell")

strDesktop = objShell.SpecialFolders("Desktop")

If Right(strDesktop,1) <> "\" Then

strDesktop = strDesktop & "\"

End If

Set objShell = Nothing

objFSO.Copyfile strSource,strDesktop

Set objFSO = Nothing

MsgBox "Update complete!",,"Complete!"
 
You can try and allow multiple users into the same mdb, but the result is
VERY poor raillery.

Read the following, as I not only explain how, but "why" you split.

I think it is much better to explain "why", then just to tell you.

So, take a quick read of the following article, it is easy, and not
technical, but you will walk away with a CLEAR sense as to why you need to
do this...

http://www.members.shaw.ca/AlbertKallal/Articles/split/index.htm
 
Dirk Goldgar said:
"Raillery"?
Click to expand...


LOL!!!

Ok, you silly goose!...

Anyone want to explain how the OE spell check works, or does not work???

Reliability was the word I was looking for!!
 
Albert D.Kallal said:
LOL!!!

Ok, you silly goose!...

Anyone want to explain how the OE spell check works, or does not
work???

Reliability was the word I was looking for!!
Click to expand...

Ah. I kind of thought that might be it, but I was so amused by the
spell-checker's choice I had to comment on it. Of *course* "raillery"
must be what you meant -- people use that word all the time! :-/
 
Back
Top