Invalid Argument error...

[Guest]

My company uses the popular off-the-shelf business system called Sage Line
500. The system is based around a SQL Server database, and over the years the
company has developed a large number of reports from the data using Access
linked to the SQL Server data by ODBC.

These have run without any trouble for months, if not years, until
yesterday. All of a sudden various queries (seemingly randomly) generate an
"Invalid argument" error when run.

Last Friday, our IT support partners came to do a routine housekeeping
session. They ensured all the critical updates on the network servers and the
Sage Line 500 server were installed, checked the anti-virus status of the
servers and the clients, updating where necessary and resolved a number of
outstanding niggles. I guess the problem could have stemmed from any one of
the many changes they made.

I know this is a support issue rather than a normal discussion group topic,
and obviously we are getting out IT parners on the case. But they may have to
search for days to find the cause. I'm hoping this experience may ring a few
bells with someone out there, and maybe point me towards the likely things to
check out.

Here's hoping. Many thanks to you all.

Vaughan

 

[Jeff Boyce]

Vaughan

The same queries now always have a problem, or queries, at random,
spontaneously develop the problem, then heal themselves?

One place I would look is the "References" (open a module, click
Tools|References). If a Reference is prefixed with "MISSING", Access has
lost track of some of the functions/features it needs.

 

[Guest]

Hi Jeff

Certain queries are consistently a problem. Others had a problem and then,
as you said, "healed themselves".

Complexity might possibly be a factor. One of the queries that consistently
generates the error has an outer join between three fields common to two
Select queries.

I looked for missing references first-off, but there aren't any.

 

[Jeff Boyce]

Vaughan

If you "suffered" an update to the data access components, formerly
acceptable syntax may now cause an error -- I've run into that.

On your more complex queries, what happens if you break it into a series
("chain") of queries building on each other. That is, instead of a single
query with all the joins, can you build a successful query that only has a
single join? Then add that query in as part of a second to pick up the
second join? ...

 

[Guest]

Thanks Jeff

I will try simplifying the queriesand see if that helps.

Regards

Vaughan