odbc to foxpro close query high memory

[Guest]

I have Access Frontend with odbc to foxpro data. Can get to data in 2gb
foxpro table, open in query or report, then close report. Task Mgr shows
Access at 0 CPU and 120mb+. Try to open again and Access locks up. Is there
a better way to 'close' the query or report - or do I need to code something
on the close? I'm at a loss and would appreciate any/all feedback. Thanks!

 

[Cindy Winegarden]

Hi Judy,

Is your FoxPro table really 2GB? 2GB is the size limit for FoxPro files.
(DBF, FPT, CDX each count as one file)

 

[Guest]

Hi Cindy,
I just verified that the largest table (trans.dbf) is 1.27gb. Its a table
of every transaction happening in this company. They have an old system
written on top of FoxPro (although no one in the company knows anything about
FoxPro). I am creating an Access frontend so they can get to the data for
analyzing only - no editing - only query viewing and reporting.

I found another post where someone mentioned in the DSN setup Options to
deselect the 'Fetch Data in Background' so I'm trying that now. Also, could
the Access lockup be caused due to errors in the query and/or report. With
the ODBC connection I am just not getting an error?

Thanks for any info...JudyG