Re: multi-user combo-box refresh not working

Tech-Archive recommends: Fix windows errors by optimizing your registry

i can't think of any reason that *not* splitting a multi-user database would
be preferable to splitting it. even if each user's frontend is on a server
rather than their PC's hard drive, that's still a better option than a
monolithic database being accessed by more than one user at a time. the
problem you're experiencing is just one of many that crop up in your current
setup.

i'd really recommend a split. suggest you post your reasons for *not*
splitting; perhaps you'll get advice on how to overcome whatever
difficulties you think would be caused by a split FE/BE database with one FE
for each user.

hth


"wineguy via AccessMonster.com" <u48580@uwe> wrote in message
news:8fe83a6c1e389@xxxxxx
I've read through a number of posts and tried many of the ideas &
suggestions.
. apart from splitting the database, which is not a preferable option at
this point, I'm just wondering what I am missing... the scenario is rather
simple, a form that is persistenly open with combo box that has a simple
query of two tables (Item and Inventory linked by item number)... the form
simply selects an item, reduces the qty, and re-displays for the next item
sold with the adjusted qty... this works as a single user, but when there
are
multiple users acting on the same instance, the refresh after the update
doesn't reflect the change... I've tried requery after update... closing
tables... requery before update... refresh... requery the form after
update...
with no luck... while splitting the database is probably a more efficient
design, it seems that this simple task should run as a single instance...
any
help or thoughts would be greatly appreciated...

thanks in advance,

glynn

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/Forums.aspx/access-modules/200901/1



.

Relevant Pages

  • multi-user combo-box refresh not working
    ... apart from splitting the database, which is not a preferable option at ... this works as a single user, ... multiple users acting on the same instance, ...
    (microsoft.public.access.modulesdaovba)
  • Re: Split Database Question
    ... reason for splitting the database and giving everyone their own copy of the ... front end is to avoid corrupted database files. ... their local machine and everything works fine. ...
    (microsoft.public.access.forms)
  • compiler and metadata, request opinions...
    ... a lot of the upper/middle compiler machinery is still lacking (such as ... embed the metadata directly into the object modules (the reason being that ... request for a particular piece of information is embedded in a symbol (sort ... it will be loaded into an in-memory version of the database. ...
    (comp.compilers)
  • misc: compiler and metadata...
    ... a lot of the upper/middle compiler machinery is still lacking (such as ... embed the metadata directly into the object modules (the reason being that ... request for a particular piece of information is embedded in a symbol (sort ... it will be loaded into an in-memory version of the database. ...
    (comp.lang.misc)
  • Re: restrict design access
    ... "Jack Leach" wrote: ... MS ActiveX Data Objects 2.1 Lib ... References play no part in splitting a database... ...
    (microsoft.public.access.modulesdaovba)