Re: Invalid Argument error...
From: Vaughan (Vaughan_at_discussions.microsoft.com)
Date: 02/22/05
- Next message: Renwick: "Re: ambiguous outer joins"
- Previous message: Don: "Re: Employee Emergency"
- In reply to: Jeff Boyce: "Re: Invalid Argument error..."
- Next in thread: Jeff Boyce: "Re: Invalid Argument error..."
- Reply: Jeff Boyce: "Re: Invalid Argument error..."
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 22 Feb 2005 03:55:02 -0800
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" wrote:
> 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.
>
> --
> Good luck
>
> Jeff Boyce
> <Access MVP>
>
> "Vaughan" <Vaughan@discussions.microsoft.com> wrote in message
> news:BD4417D3-E32F-4D56-B29F-F5F49A257A4F@microsoft.com...
> > 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
> >
> >
>
>
- Next message: Renwick: "Re: ambiguous outer joins"
- Previous message: Don: "Re: Employee Emergency"
- In reply to: Jeff Boyce: "Re: Invalid Argument error..."
- Next in thread: Jeff Boyce: "Re: Invalid Argument error..."
- Reply: Jeff Boyce: "Re: Invalid Argument error..."
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|