04-11-2007 08:28 AM
04-11-2007 08:29 AM
04-12-2007 04:35 PM
04-12-2007 08:34 PM
04-13-2007 10:59 AM
Hi Jim,
No, I am not sure why you are experiencing this difference in load behavior. We tried to replicate your situation here and were able to successfully load either by selecting the whole table or specific columns within that table:
ACCESS Table with 7 columns, each column with 560 000 values
Tested on both a DIAdem 9.1 SP2c computer and a DIAdem 10.1 SP1 computer (clean installs)
Result in DIAdem:
7 channels, each channel with 560 000 values if I load the table complete
3 channels, each channel with 560 000 values if I load selected channels
The first step is for us to reproduce your symptoms. Would it be possible for you to post your Access database on our ftp.ni.com/incoming server?
How much RAM do you have on your computer?
Brad Turpin
DIAdem Product Support Engineer
National Instruments
04-13-2007 11:11 AM
Brad,
I agree, it should not make a difference but for some reason it is. I can try to upload the database but it is about 650MB - is that a problem (other than the time to upload it).
Also, my system has 1.5GB of RAM. Once the database is loaded, the queries are the ones exhibiting this behavior (i.e. #141_LTOE, etc.)
04-13-2007 11:33 AM
Hi JimNoel,
650 MB will be fine for ftp.ni.com/incoming.
04-13-2007 11:48 AM
04-16-2007 01:18 PM
Hi Jim,
I have downloaded your Access data base file and am playing around with it. Could you please tell me which view table you were loading columns from that resulted in the 700,000+ records?
Also, do you really want to load all the records from those columns, or do you in fact want to query a subset of those records which satisfy certain relational conditions?
Brad Turpin
DIAdem Product Support Engineer
National Instruments
04-16-2007 01:38 PM