M
Mark Andrews
I understand that an mdb file can not be greater than 2Gb in size, so... if
there were several databases with, say, nearly 2Gb in each then I guess
there is no problem linking a front end to each of the mdbs, but... can jet
handle a query in the front end that links some of those tables together to
produce a recordset containing the equivalent of far greater than 2gb worth
of data..??? (Assuming adequate system resources.)
A more direct example would be trying to union 2gb of data from two or more
databases - is the limitation purely on the mdb size or ultimately with the
volume of data jet can handle regardless of how you spread the data out.
I have a short term issue and an extremely complex access system that makes
upsizing to SQL server a non-starter. Can I effectively spread more than 2Gb
of data over several mdbs but combine it with queries / recordsets?
Uncharted territory perhaps but needs must!
Any thoughts/experience greatly appreciated.
Mark Andrews
there were several databases with, say, nearly 2Gb in each then I guess
there is no problem linking a front end to each of the mdbs, but... can jet
handle a query in the front end that links some of those tables together to
produce a recordset containing the equivalent of far greater than 2gb worth
of data..??? (Assuming adequate system resources.)
A more direct example would be trying to union 2gb of data from two or more
databases - is the limitation purely on the mdb size or ultimately with the
volume of data jet can handle regardless of how you spread the data out.
I have a short term issue and an extremely complex access system that makes
upsizing to SQL server a non-starter. Can I effectively spread more than 2Gb
of data over several mdbs but combine it with queries / recordsets?
Uncharted territory perhaps but needs must!
Any thoughts/experience greatly appreciated.
Mark Andrews