Hi all,
I work developing Access Databses using Microsoft Access 2000. The database
is pratically bug free now and all problems seem to be ironed out. That is
until we get a phone call saying something does not quite work. The answer,
well it works here in the office on my computer, but transfer the same
IDENTICAL database to another persons computer and bang, something goes
wrong, I try to replicate the error but can't. Why is this? Is this typical
access database?

For example, in one case, a simple drop down box with a list of names in it,
no filters, nothing, very simple. Yet when sent out and run on the clients
computer, they click the drop down box and only half the items in the list
appear, why I ask? Try it again here on my computer and works fine no
problems.

This is just one example of many occurances and this is getting very
annoying for me now. Any advice?

Many thanks.
Ash.

There are 2 possiblities that I can think of. First is references. Open any
code window on both machines and make sure they match. If they don't or any
are marked as missing, correct them for each machine. References are unique
to machines and can pose a problem in any system.

The second problem may be Access 2000 itself. I always considered it to be
buggy, at least during development. Usually, during production databases
worked fairly well. My suggestion would be to move to Office XP or 2003, if
possible. If not, make sure all the service packs are installed.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com

"AshGrant" <(E-Mail Removed)> wrote in message
news:C6B8E97C-BAAD-4C4F-8672-(E-Mail Removed)...
> Hi all,
> I work developing Access Databses using Microsoft Access 2000. The
> database
> is pratically bug free now and all problems seem to be ironed out. That is
> until we get a phone call saying something does not quite work. The
> answer,
> well it works here in the office on my computer, but transfer the same
> IDENTICAL database to another persons computer and bang, something goes
> wrong, I try to replicate the error but can't. Why is this? Is this
> typical
> access database?
>
> For example, in one case, a simple drop down box with a list of names in
> it,
> no filters, nothing, very simple. Yet when sent out and run on the clients
> computer, they click the drop down box and only half the items in the list
> appear, why I ask? Try it again here on my computer and works fine no
> problems.
>
> This is just one example of many occurances and this is getting very
> annoying for me now. Any advice?
>
> Many thanks.
> Ash.

Thanks for the reply!
As for your first suggestion, the references are identical, this is check
thoroughly when the machines are initially setup by us.
The problem is, we cant have both machines sat next to each other and do a
spot check since ours is down in hampshire, in our office and the others are
dotted all over the UK, from Benbecula (scottish islands) to lincolnshire to
plymouth to scotland.
A move to Office 2003 sounds interesting and I will probably end up putting
this suggestion forward to my boss.

When you mentioned you found access 2000 to be "buggy", what kind of
problems did you encounter? I wonder if any of them match mine?

Thanks again.
Ash.

"Arvin Meyer [MVP]" wrote:

> There are 2 possiblities that I can think of. First is references. Open any
> code window on both machines and make sure they match. If they don't or any
> are marked as missing, correct them for each machine. References are unique
> to machines and can pose a problem in any system.
>
> The second problem may be Access 2000 itself. I always considered it to be
> buggy, at least during development. Usually, during production databases
> worked fairly well. My suggestion would be to move to Office XP or 2003, if
> possible. If not, make sure all the service packs are installed.
> --
> Arvin Meyer, MCP, MVP
> http://www.datastrat.com
> http://www.mvps.org/access
> http://www.accessmvp.com
>
> "AshGrant" <(E-Mail Removed)> wrote in message
> news:C6B8E97C-BAAD-4C4F-8672-(E-Mail Removed)...
> > Hi all,
> > I work developing Access Databses using Microsoft Access 2000. The
> > database
> > is pratically bug free now and all problems seem to be ironed out. That is
> > until we get a phone call saying something does not quite work. The
> > answer,
> > well it works here in the office on my computer, but transfer the same
> > IDENTICAL database to another persons computer and bang, something goes
> > wrong, I try to replicate the error but can't. Why is this? Is this
> > typical
> > access database?
> >
> > For example, in one case, a simple drop down box with a list of names in
> > it,
> > no filters, nothing, very simple. Yet when sent out and run on the clients
> > computer, they click the drop down box and only half the items in the list
> > appear, why I ask? Try it again here on my computer and works fine no
> > problems.
> >
> > This is just one example of many occurances and this is getting very
> > annoying for me now. Any advice?
> >
> > Many thanks.
> > Ash.
>
>
>

This may sound strange but the error you mention saying that not "all
the items in the dropdown box don't appear". This sounds like you are
missing data from the database.
If you have it set up as a front end back end - are they pointing to the
same database with all the names?

Other actual error messages would be of more help. Or if it is more
situation like this then that should be your problem.

--
Craig Hornish

Visit weekly Access conferences
Tuesday, 11:00am-12:30pm (Eastern US)
Thursday, 3:30pm- 5:00pm (Eastern US)

http://community.compuserve.com/n/pf...g=ws-msdevapps

"Think outside the box, because anything is possible."
"How long it will take or whether it requires divine intervention is another
issue"

"AshGrant" <(E-Mail Removed)> wrote in message
news:C6B8E97C-BAAD-4C4F-8672-(E-Mail Removed)...
> Hi all,
> I work developing Access Databses using Microsoft Access 2000. The
> database
> is pratically bug free now and all problems seem to be ironed out. That is
> until we get a phone call saying something does not quite work. The
> answer,
> well it works here in the office on my computer, but transfer the same
> IDENTICAL database to another persons computer and bang, something goes
> wrong, I try to replicate the error but can't. Why is this? Is this
> typical
> access database?
>
> For example, in one case, a simple drop down box with a list of names in
> it,
> no filters, nothing, very simple. Yet when sent out and run on the clients
> computer, they click the drop down box and only half the items in the list
> appear, why I ask? Try it again here on my computer and works fine no
> problems.
>
> This is just one example of many occurances and this is getting very
> annoying for me now. Any advice?
>
> Many thanks.
> Ash.

In article <C3274ED1-EA53-476B-ABA3-(E-Mail Removed)>,
(E-Mail Removed) says...

>
> When you mentioned you found access 2000 to be "buggy", what kind of
> problems did you encounter? I wonder if any of them match mine?
>

Access 2000 had some problems in VBA code stability and was more prone
to corruption, among other things. However, I don't remember any
problems that would cause just "some" of the records to be missing from
a combobox dropdown.

I think it's much more likely that something else is happening with the
back-end data at the other locations.

Can any of the users run a full MDB? When this problem occurs, you
could help the user hit Ctrl-G for the Immediate Window and check the
value of the Rowsource of the combobox, and paste that SQL statement in
a new query to check it out. You can even do it for them if you use
some kind of remote assistance utility.

--
Armen Stein
Microsoft Access MVP
www.JStreetTech.com

AshGrant wrote:
> For example, in one case, a simple drop down box with a list of names in it,
> no filters, nothing, very simple. Yet when sent out and run on the clients
> computer, they click the drop down box and only half the items in the list
> appear, why I ask?

Check Tools | Options | Edit/Find for the setting "Don't display lists where
more than this number of records read." Is it the same number on all
computers? The default is 1000 so yours might display 2,000 names if you
changed this limit, but other computers only show half as many if they
haven't changed the number too.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200611/1

Thanks for all of your suggestions! I must admit I havent checked the options
under edit/find for max records, will look into that one Monday.
One of the first things i did to check this problem out was to look for
irregularities in the data table concerned. Everything seems fine though, BUT
could null values possibly be causing the problem? I have null values in some
fields which arent used in the combo box record source but may they still
effect in some way perhaps?
Also yes they do use a full MDB, and yes we use a remote assisstance utility
(pcanywhere), i will check out that immeadiate window suggestion too.
Thanks again.

If anyone else has experienced similar problems to this, i.e. the "it works
here but not there" scenario then please let me know, with the correct
feedback i can put this thread forward to my boss and advise of an upgrade to
office 2003...

Thanks again
Ash.

"Granny Spitz via AccessMonster.com" wrote:

> AshGrant wrote:
> > For example, in one case, a simple drop down box with a list of names in it,
> > no filters, nothing, very simple. Yet when sent out and run on the clients
> > computer, they click the drop down box and only half the items in the list
> > appear, why I ask?
>
> Check Tools | Options | Edit/Find for the setting "Don't display lists where
> more than this number of records read." Is it the same number on all
> computers? The default is 1000 so yours might display 2,000 names if you
> changed this limit, but other computers only show half as many if they
> haven't changed the number too.
>
> --
> Message posted via AccessMonster.com
> http://www.accessmonster.com/Uwe/For...ccess/200611/1
>
>

AshGrant wrote:
> I have null values in some
> fields which arent used in the combo box record source but may they still
> effect in some way perhaps?

If the nulls aren't in the criteria (WHERE clause or HAVING clause), and they
aren't in columns used in the joins, and they aren't displayed as columns in
the combo box row source query, the nulls don't have any effect on the number
of records shown.

> If anyone else has experienced similar problems to this, i.e. the "it works
> here but not there" scenario then please let me know

We've had this *lots* of times, but we were always able to trace it to
different settings on the different computers, different paths, different
user permissions, different Access/Jet versions and service packs, and user
errors.

--
Message posted via AccessMonster.com
http://www.accessmonster.com/Uwe/For...ccess/200611/1

1. What kind of network is the other database running on? Novell networks use
to have problems with the number of records, but I thought that was fixed
about 5 years ago.

2. How many records are in the combo box? Access runs out of steam at around
32,000 records and sometimes sooner.
--
Jerry Whittle
Light. Strong. Cheap. Pick two. Keith Bontrager - Bicycle Builder.


"AshGrant" wrote:

> Hi all,
> I work developing Access Databses using Microsoft Access 2000. The database
> is pratically bug free now and all problems seem to be ironed out. That is
> until we get a phone call saying something does not quite work. The answer,
> well it works here in the office on my computer, but transfer the same
> IDENTICAL database to another persons computer and bang, something goes
> wrong, I try to replicate the error but can't. Why is this? Is this typical
> access database?
>
> For example, in one case, a simple drop down box with a list of names in it,
> no filters, nothing, very simple. Yet when sent out and run on the clients
> computer, they click the drop down box and only half the items in the list
> appear, why I ask? Try it again here on my computer and works fine no
> problems.
>
> This is just one example of many occurances and this is getting very
> annoying for me now. Any advice?
>
> Many thanks.
> Ash.

MDB is too inconsistent for real world use.

Don't use it for a single record and a single record
spit on the person that used it in the first place

fire anyone that likes it

MDB isn't reliable enough for real world use.
Dont listen to these fat senile assholes.. MDB is DED

Use Access Data Projects



AshGrant wrote:
> Hi all,
> I work developing Access Databses using Microsoft Access 2000. The database
> is pratically bug free now and all problems seem to be ironed out. That is
> until we get a phone call saying something does not quite work. The answer,
> well it works here in the office on my computer, but transfer the same
> IDENTICAL database to another persons computer and bang, something goes
> wrong, I try to replicate the error but can't. Why is this? Is this typical
> access database?
>
> For example, in one case, a simple drop down box with a list of names in it,
> no filters, nothing, very simple. Yet when sent out and run on the clients
> computer, they click the drop down box and only half the items in the list
> appear, why I ask? Try it again here on my computer and works fine no
> problems.
>
> This is just one example of many occurances and this is getting very
> annoying for me now. Any advice?
>
> Many thanks.
> Ash.