well i already checked it up on 3 PCS out of which 2(1 was fresh) were showing the problem in VB IDE itself. another one was there which was not in problem in IDE but after making the exe and running exe on same PC, the exe was giving same problem.
so sounds quite strange. mean code does'nt have any problem as prior to mdac2.6 it was working fine and even after 2.6 inst. on one PC it was fine.

but i then thought of looking into code, i dont know may be it sounds stupid but i was let's say having one combo DCB1 one adodc ADC1, i was using that combo to retreive a list only. The properties i set for DCB1 were datasource and rowsource as ADC1 (select * from emp for ex), listfield as emp_name, boundcolumn and datafield as emp_cd.

so i set datafield to none and everything is fine.
i think i wasted ur time and mine also, sorry for that.

i dont know but what i got is datafield is needed when u use 2 different ADODC so when u pick listfield from one dc, it sends datafield to another DC, in my case both DC were same so may be that was a problem.

am i right plz correct me if i'm wrong...
and one more thing y that erroneous appl worked on one PC. the old application is still running fine on client side with mdac 2.5