Search results

to go into slightly more detail - there are two versions of my code, one - a simplified analysis, which runs equally fast under 97 and 2000 and the other, an advanced analysis which basically involves an additional string to string join in all queries which upon upgrading to 2000 runs...

i'm in the process of debugging code in vb which implements sql strings, having upgraded to access 2000/2 and have noticed that the whilst the sql queries are doing there thing correctly, the sort order of the tables is quite different although the sql is identical - it appears that 2000/2 is...

pat, again you have come to my rescue! thank you. Could you reccommend a resource that would highlight any other issues that I may encounter between 97 and 2002 regards Ian

help! (again!!) i've noticed that under access 2000/2002 select into queries are giving integer values where previously they were double precision, which is messing up my results in a major way is there an easy work around or do I have to change to using a create table (specifiying the...

thanks again pat, could you give me a pointer to the vba approach thnks

Hi, I'm trying to import csv files which have a header of three lines, the third of which contains the column heading names, the other two are either blank or contian the file name info. How do I import the file correctly so that the data is all in the right columns and I don't have to import...

cheers everyone, you've set my mind at ease.. but only = null seems to work in other parts of the query i.e. update table set variable = null where another variable is null ! which of course is also used lots in my program, so a global replace would be messy :rolleyes: Ian

Hi all, first time here! I've just been upgraded at work to access xp from 97 and notice that, in my vb programs where I use strings to fire off sql to access, the WHERE variable = NULL no longer works and I have to change them all to WHERE variable IS NULL is this correct or have I messed up...