March 12, 2007 at 7:58 am
good luck; it's been a while since i fiddled with access, but i remember access 2000 had a 255 column limit; maybe the more updated version might not have that limitation;
I looked to see if the ADODB.Recordset had a limitation, but it appears that it does not, it only has a limitation imposed by the provider...ie the JET driver would impose a limit of 255, the SQLOLEDB provider a limit of 1024, etc... on it...so in theory, a disconnected recordset might not have the limitation(except the limitation of available memory on the box?);
maybe you can do your analysis in a program, and insert just the final results into a SQL table.
Lowell
March 12, 2007 at 8:23 am
Thanks Lowell for the info!
Unfortunately, the Analysis process takes months - thus requiring permenant storage and fast data access!!
Regards,
TNT
March 12, 2007 at 6:09 pm
TNT,
Just for grins, can you post the "header file" and a row or 2 of data (making sure, of course, there are no SSN's, account numbers, etc in the file)? I've got this nasty little idea in my head...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 30, 2007 at 8:08 am
Hi Jeff
Apologies for the late response!
I have posted the files you requested!
HEADER FILE
<FIELD name="FIELD1" offset="1" length="8" type="D" />
<FIELD name="FIELD2" offset="9" length="10" type="N" />
<FIELD name="FIELD3" offset="19" length="43" type="S" />
<FIELD name="FIELD4" offset="62" length="10" type="N" />
<FIELD name="FIELD5" offset="72" length="10" type="N" />
</FIELDS>
193810231197410064hkworaepxvefmrsjsdgciptemyllbdtbmdjevoppijq243276826 265713799
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply