similar to: RODBC and Microsft Visual C++ Runtime Library

Hi, I am trying to use sqlSave to write a dataframe to an existing table in a DB2 database. The database contains two schemas. My experience is the following: (1) in the case that tablename is left empty in sqlSave, R writes to the instance level schema (2) in the case that a tablename is specified and that table name exists only once in the database, R will write to that table irrespective

I have an existing table, and I am trying to use sqlSave to append additional rows to this database. I omit the primary key, which is a uniqueidentifier type (MS SQL), so that the database can populate that field. However, I get the following error: > sqlSave( ch, result, tablename=thetablename, append=TRUE, rownames=FALSE, colnames=FALSE ) Error in odbcUpdate(channel, query, mydata,

Hello, I contact you after having unsuccessfully asked my question to R mailing list. I use the package RODBC to connect to a MS-SQL server. I am able to getQuery from the database. I am now studying the sqlSave some data into the database. Unfortunetly, I meet some issues relating to the format of the data that arrives into the database. I have three columns. The first one should be in the

Till yesterday I was more than satisfied by RODBC, specifically by sqlSave which I had been happily using in a daily crontab R batch job regularly updating a postgresql db for as long as one year. In this R- batch I was able to save records into indexed tables *** even though *** they already existed. in this case sqlSave simply neglected those rows of the input table that were offending the

Good day, all. I just upgraded to R 2.6.0. I re-installed my most-used packages including RODBC to be sure I'm up-to-date. I have been working with a large insurance claims dataset stored in a MS-Access database on a Windows machine. I have been regularly exporting tables from R into it using sqlSave. It's worked like a charm until today, when this happened: >

Hi, I am hoping to use the RODBC package to write a dataframe to an Excel .xlsx file. The dataframe contains at least one field with character elements that exceed 255 bytes, which appears to be the cell width limit in Excel. Below is example code and the warning message received: library(RODBC) d <-

I am running R version 2.8.1 on Windows XP OS. This works fine. (Data.frame dta is created with records from the DB2 table.): sql <- "select * from storage.testappend_slt order by uut" dta <- sqlQuery(channel,sql) But when I try to append records (from data.frame newdta) to the same DB2 table. I get an error: sqlSave(channel, newdta, tablename = storage.testappend_slt, append

I can create a temp table with MySQL and R DBI[1], but I don't see how to do the same with Microsoft SQL 2005 and RODBC. R 2.8.1 creates the table, but then it can never see it. I'm looking to avoid replacing the convenience functions like sqlSave(). [1] https://stat.ethz.ch/pipermail/r-help/2009-March/190033.html > library(RODBC) > channel <-

Hi Michael, Here is the result of my first testing: (0) Dr. Watson Sorry, I should have given a more precise description: by default in R exists a function with the name 'table', if you use this name as in odbcPrimaryKeys(0, table) a Dr. Watson occurs, because table does not give a table name. However, it is always a good idea to prevent Dr. Watsons, even if it is triggered by a

Hello, After a (bad) first try some months ago, I'm trying again to use RODBC package instead of DBI+RMySQL packages to populate MySQL database. The main command is sqlSave(channel, data_df, tablename, append=T, rownames=FALSE, colnames=FALSE, fast=FALSE, varTypes=vartypes) where data_df is the data.frame I want to save and vartypes is obtained following the tip given here

Hello! I have no problem reading Excel files (each worksheet in the file is a "table" which can be read - at least in my case). What I would like to do is to read such a table, change it (just the contents, not the format) and write it back, and this I can not do. I am getting the following error messages (3 slightly different attempts): > sqlSave(con, x, tablename =

I am using R-2.10.1 binary from CRAN on a WinXP Pro system. I also use SAS v9.2 on the same box. I just started using the SAS ODBC driver that comes with version 9 of SAS. I have been able to set up an ODBC source for SAS datasets using the driver, and then with RODBC I am able to read a sample SAS dataset. > library(RODBC) > ch <- odbcConnect('sasodbc', believeNRows=FALSE)

Dear R users, I've learned today about RODBC package in order to import xls file to dataframes and export the dataframes to xls files. However I have some problems. Please excuse me if these are basic but as I said, I've just begun with this package. Also this email is quite long, but everything is related, so I don't think it would be better to split it. Moreover, there's a

Hi, I've written some code that fetches data from an Access Database (2003), processes the data, then saves the modified data back into a table in the Access database. It works if I only pass through the code once, but if I put a loop around the code so that I fetch data from a different source table, and then save it again to a different destination table, the code crashes. It is

Dear All, Using RODBC I have read in a (429 x 11) dataframe from Access, and would like to append two columns of transformed data (429 x 2) to the original table (thereby making it a 429 x 13 table). I would ideally like this to be the same name etc as the original table in Access. I have used the following command: R>

I am running R version 2.8.1 on Windows XP OS. recs is a one-row, eighteen-column data.frame I want to insert into a DB2 table. sqlSave(channel, recs, tablename = "testappend_slt", append = TRUE, + rownames = FALSE, colnames = FALSE, + verbose = TRUE, oldstyle = FALSE, + safer = TRUE, addPK = FALSE, + fast = FALSE, test = FALSE, nastring = NULL) Query:

I am running R version 2.9.2 on Windows XP OS with RODBC version Version: 1.3-0. Has anyone out there in the R user community successfully appended records to a DB2 table on a remote database using the sqlSave function in the RODBC package? (or by any other means from R?) I posed a similar question a few months ago and unfortunately, did not receive a response. I was hoping recent upgrades to

Buen dia Javier, muchas gracias por tu ayuda y el script compartido. Me va a servir como ayuda para seguir aprendiendo sobre RODBC pero no encuentro una solucion para este problema puntual de poder definir el tipo y ancho de las variables, q segun creo se hace con el argumento varTypes. Si alguien tien algun ejemplo donde haya usado la SqlSave y VarTypes, me sera de gran ayuda. Abrazo a todos

Hola Javier, si no estoy entendiendo mal, lo q deseo hacer no se trata de configurar los parametros SQL, sino solo de colocar un vector en el argumento VarTypes de la funcion sqlSave. El manual especifica esa opcion, pero no da ningun ejemplo de como usarla. *varTypes an optional named character vector giving the DBMSs datatypes to be used for* *some (or all) of the columns if a table is to be

Hi, I've got a problem with RODBC and saving (sqlSave) of a dataframe in Access. R 2.0.1 is running on windows XP. When executing the examples in R help for the "USArrests" data set "sqlSAve" works fine, but running sqlSave() for a dataframe "Adat" > str(Adat) `data.frame': 1202 obs. of 18 variables: containing 18 columns and ca. 1200 rows fails.