search for: sthelier

Dear lists, It seems that RODBC has a problem : when reading through ODBC from an Access table with missing values, *character* missing values are (correctly) reported as NA factor values. *Numeric* values, however, retain the value of the same variable in the previous row. My setup : R 1.1.1 under Win95, RODBC as compiled with the R Win CRAN distribution, MS Access 97. I just discovered this,

Dear lists, It seems that RODBC has a problem : when reading through ODBC from an Access table with missing values, *character* missing values are (correctly) reported as NA factor values. *Numeric* values, however, retain the value of the same variable in the previous row. My setup : R 1.1.1 under Win95, RODBC as compiled with the R Win CRAN distribution, MS Access 97. I just discovered this,

Full_Name: David Whiting Version: 2.1.0 Under development (unstable) OS: linux Submission from: (NULL) (82.39.106.169) I have just upgraded from a previous version (2.0.0?) and found some of my code that used okay to run now gives an error. The function being called is sqlSave(). I am pretty sure (but not 100% certain) that the data frame I am trying to save has not changed. I am 100% sure that

Dear R-fans, My database access package RODBC is now available on CRAN. For those who have never used it, odbc is a database and platform independant API which provides an SQL interface to a large number of database engines. The databases supported include not only SQL based RDBMS but also CSV files, foxbase, dBase, MSExcel etc. ODBC has been promoted mainly by Microsoft and this is where the

Dear R-fans, My database access package RODBC is now available on CRAN. For those who have never used it, odbc is a database and platform independant API which provides an SQL interface to a large number of database engines. The databases supported include not only SQL based RDBMS but also CSV files, foxbase, dBase, MSExcel etc. ODBC has been promoted mainly by Microsoft and this is where the