 |
|
 |
aak_neo Level: Scholar

 Registered: 11-02-2007 Posts: 30
|
Re: large no. of records in db causes application to slow down
yes u are absolutely correct in guessing that my sql selects all fields but thats so coz its required as per the application.
my db has foll. fields id,date,time, ch1,ch2,ch3,ch4,ch5,ch6,ch7,ch8 where chx are channel voltages. each day about
24x60x60=86400 records get added in the db. i thought of distributing as 1 db per day having 24 tables corresponding to each hour. now this will also do for me
but there is a form in my project which displays on chart some of these records by
1.getting the start day,start time from user(gives start_id)
2.getting the end day,end time from user(gives end_id)
3. display the data in between these id's on chart
with one table & one database it seems simple.But with even two tables it will coz problems as how will i be able to fill a recordset
with data from two or more different tables. a recordset i m saying as chart needs one recordset to display data.
can i fill a recordset with data from different tables? or do u suggest i should use a different db altogether to get the desired recordsource?
____________________________
You never see past the choices you don't understand
|
|
05-03-2007 at 04:20 PM |
|
|
|
|
 |
 |