No. I've traced the offending query to the following SQl statement.:
SELECT [MPM WBS Table].[WBS or NWA], [MPM WBS Table].Parent, Sum([EOC Data
Table].[BCWS Hrs]) AS [SumOfBCWS Hrs], Sum([EOC Data Table].[BCWS Cost]) AS
[SumOfBCWS Cost], Sum([EOC Data Table].[ETC Hrs]) AS [SumOfETC Hrs], Sum([EOC
Data Table].[ETC Cost]) AS [SumOfETC Cost], Sum([EOC Data Table].[BCWP Hrs])
AS [SumOfBCWP Hrs], Sum([EOC Data Table].[BCWP Cost]) AS [SumOfBCWP Cost],
Sum([EOC Data Table].[ACWP Hrs]) AS [SumOfACWP Hrs], Sum([EOC Data
Table].[ACWP Cost]) AS [SumOfACWP Cost]
FROM [EOC Data Table] INNER JOIN [MPM WBS Table] ON [EOC Data Table].[WBS
ID] = [MPM WBS Table].[WBS or NWA]
WHERE ((([EOC Data Table].YYYYMM)<=200810))
GROUP BY [MPM WBS Table].[WBS or NWA], [MPM WBS Table].Parent;
This works if the "WHERE" is >200810, but not for values <=200810. (This is
actually a date range in YYYYMM format.) It even overflows even for YYYYMM
between 200805 and 200810.
"Mike" wrote:
> Are you dividing in you query
>
> "DHM" wrote:
>
> > I am using VBA in Excel to open an Access2003 database (~150M in size). It
> > worked fine but now I'm seeing an overflow error (#6) when I do an
> > OpenRecordset. Are there any ways to avoid this problem without using
> > Server? I ran the compress/repair option on the database and split the
> > database between tables and queries with no luck. ALSO, if I move to
> > Server, will I still have this problem, i.e., is it a recordset size problem
> > in EXCEL?
> >
> > Thanks,
> > -David
|
Similar Threads
