Union Query works on my PC's but not on clients machines

[Ray]

Hi sorry to say I am back with the same old problem.

I have a union query that works perfectly on two machines at home but not on
two office machines there I get a message that says it is either
incorrectly typed or is too complicated. My question is how can that be
given it works on other machines?

One machine is set up in a similar way to the one that fails. The First is
a notebook with 1GB. Initially I wondered about the memory but that would
not seem to be relevant given that the other machine that work has the same
memory (512MB).

The biggest part of the problem is that the machine it is to run on is the
one on which it doesn't work.

When I last posted the following was suggested by Van T. Dinh

* The copy of the database may be corrupted. Try a fresh copy of the
database from the working PCs on the problem PC.

* Windows and Access use a lot of files and the machines may have different
file versions, especially that there are so many Updates / Service Releases
/ Service Patches.

Suggest you apply all available Updates / SRs / SPs for bothe Windows and
Office/Access on the problem machine and try again.

However this has not solved the problem. How can I check the file versions
of all the bits that make up Access given that I have no idea what they are
all called or where they all sit on the computer. I am sure that it has to
be a difference in Access some where.

By the way I have uninstalled and the re-installed access on one of the
office machines and updated it in the same way I updated my home PC. Still
no joy.

I am lost and desperately need help with this. The client is being very
patient but I am loosing mine.

Ray

In desperation

 

[Allen Browne]

To check the file versions between the two machines, find these files on
your drive:
- msaccess.exe, typically under c:\program files\office\microsoft\office.
- msjet40.dll, typically in c:\windows\system32.

Right-click each file in the Windows Explorer, and choose Properties.
Check the Version tab, and look for differences.
For updates, go to:
http://support.microsoft.com/gp/sp


The "too complicated" message can also fire if Access is not able to
interpret the query for any reason.

Examples that can trigger this condition:
1. The query contains undeclared parameters, and Access is not understanding
the data types correctly.

2. The query contains calculated fields with criteria, and Access is not
understanding the data types correctly.

3. Your criteria are applied incorrectly, e.g. you don't have the quotation
marks needed around the literal values applied on a Text field, or you don't
have the # delimiters around literal dates on a date fields.

4. The parameters refer to values in a form, and the values are
inappropriate. For example, your query refers to:
[Forms].[Form1].[StartDate]
and the unbound text box contains:
2/29/2005

5. There are spaces in a field name, table name, parameter name, and you
have not enclosed the name in square brackets.

6. You have the correct number of brackets, but they are placed incorrectly
in the query.

7. You have names that clash with reserved words in SQL.

 

[Ray]

Hi Allen

Thanks so much for your very detailed reply. Because it was detailed and the
fact that I don't have constant access to the PC's at the clients offices it
has taken a while to work through things.

Just as an aside I am also a Perthite.

I am still having no success. I have worked through all your suggestions re
the triggers points 1 to 7 and cannot see anything that fits those
conditions. This brings me back to file versions. I have just followed the
link you provided again and discovered something I missed before and so I
will check all that out next time I visit the client (probably Monday).

What still puzzles me is why does it work on two PC's at home but not
others. I can now add my daughters new laptop to that list of does not work.
So far as my initial check goes it shows that I am using the very latest
version of Jet (Security Bulletin MS04-014, version 4.0.8618.0) and Access
(11.6355.6408) on all machines. I am working at a site tomorrow that has at
least ten PC's on which I can try this databse so I will see what happens
there.

Though not yet done I wanted you to know where I had got to..

I also want to thank you for your web site which I have used several times
in the past to help me work through issues. Your help on this one is also
appreciated.

Ray Brown

To check the file versions between the two machines, find these files on
your drive:
- msaccess.exe, typically under c:\program files\office\microsoft\office.
- msjet40.dll, typically in c:\windows\system32.

Right-click each file in the Windows Explorer, and choose Properties.
Check the Version tab, and look for differences.
For updates, go to:
http://support.microsoft.com/gp/sp


The "too complicated" message can also fire if Access is not able to
interpret the query for any reason.

Examples that can trigger this condition:
1. The query contains undeclared parameters, and Access is not
understanding the data types correctly.

2. The query contains calculated fields with criteria, and Access is not
understanding the data types correctly.

3. Your criteria are applied incorrectly, e.g. you don't have the
quotation marks needed around the literal values applied on a Text field,
or you don't have the # delimiters around literal dates on a date fields.

4. The parameters refer to values in a form, and the values are
inappropriate. For example, your query refers to:
[Forms].[Form1].[StartDate]
and the unbound text box contains:
2/29/2005

5. There are spaces in a field name, table name, parameter name, and you
have not enclosed the name in square brackets.

6. You have the correct number of brackets, but they are placed
incorrectly in the query.

7. You have names that clash with reserved words in SQL.

--
Allen Browne - Microsoft MVP. Perth, Western Australia.

Reply to group, rather than allenbrowne at mvps dot org.

Hi sorry to say I am back with the same old problem.

I have a union query that works perfectly on two machines at home but not
on two office machines there I get a message that says it is either
incorrectly typed or is too complicated. My question is how can that be
given it works on other machines?

One machine is set up in a similar way to the one that fails. The First
is a notebook with 1GB. Initially I wondered about the memory but that
would not seem to be relevant given that the other machine that work has
the same memory (512MB).

The biggest part of the problem is that the machine it is to run on is
the one on which it doesn't work.

When I last posted the following was suggested by Van T. Dinh

* The copy of the database may be corrupted. Try a fresh copy of the
database from the working PCs on the problem PC.

* Windows and Access use a lot of files and the machines may have
different
file versions, especially that there are so many Updates / Service
Releases
/ Service Patches.

Suggest you apply all available Updates / SRs / SPs for bothe Windows and
Office/Access on the problem machine and try again.

However this has not solved the problem. How can I check the file
versions of all the bits that make up Access given that I have no idea
what they are all called or where they all sit on the computer. I am sure
that it has to be a difference in Access some where.

By the way I have uninstalled and the re-installed access on one of the
office machines and updated it in the same way I updated my home PC.
Still no joy.

I am lost and desperately need help with this. The client is being very
patient but I am loosing mine.

Ray

In desperation