similar to: RODBC and datetimes

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,

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>

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 <-

Hi. I attempted to use RODBC and decided to execute all the tests provided in "Test.r" under the unpacked package RODBC folder. Beginning with the following: library(RODBC) library(MASS) USArrests[1,2] <- NA hills <- hills[1:15,] row.names(hills)[12] <- "Dollar ('$')" set.seed(1) # MySQL ## testdb3 is ODBC/Connector 3.51.x, testdb5 is 5.1.x channel <-

Dear R users, I have a follow-up question on sqlSave(). Since most of the output from the tests I use are lists, I would like to loop to export each element of the list and append it to the sheet. Here is what I do: > library(RODBC) > test <- structure(list(m = structure(c(0.090909090909091, 0.181818181818182, 0.272727272727273, 0.363636363636364, 0.454545454545455,

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

I am having the following problem with RODBC I connect to an oracle 8i (8.1.7) database using RODBC as follows; dbConn <- odbcConnect("mydatabase","myuserid","mypassword",case="oracle") Then I extract some data, actually a whole table; orgdata <- sqlQuery(dbConn, "select * from organism", na.strings = "NA") Then I try to save it

I'm changing some functions from storing data in SQLite (using RSQLite) to storing it in PostgreSQL (using RODBC). When trying to store very long character fields I get the following message: > sqlSave(pg, Grids, rownames = FALSE, append = TRUE) Warning messages: 1: In odbcUpdate(channel, query, mydata, paramdata, test = test, verbose = verbose, : character data truncated in column

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

Hello, All: The vignette with the sos package used "upquote.sty", required for R Journal when it was published in 2009. Current CRAN policy disallows "upquote.sty", and I've so far not found a way to pass "R CMD check" with sos without upquote.sty. I changed sos.Rnw per an email exchange with Prof. Ripley without solving the problem; see below. 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

Dear all, I using R version 2.9.0 on Windows XP and want to insert data from a data frame in R into a oracle database via sqlUpdate with the package RODBC. My example is the following: TEST0<-data.frame(NR=c(1,2,600),NAME=c("JK","TR","AR"), DATUM=c("2009-01-01","2010-01-02","2010-06-09")) If I create the table in the database with

Dear list, Being new to both the postgres database, ODBC and the RODBC interface, I am somewhat confused by some of the problems I am experiencing trying to connect R to the database. Whai I am trying is basically the example part of the help file for the sqlSave function: > library(RODBC) > odbcConnect("theodor") -> channel > data(USArrests) > sqlSave(channel,

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'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.

Début du message réexpédié : > De: Depiereux Constant <constant.depiereux@aqte.be> > Date: 16 mars 2005 00:11:11 GMT+01:00 > À: spjgmwn@iop.kcl.ac.uk > Objet: Rép : [R] RODBC, sqlSave and sqlAppend > > > Le 15-mars-05, à 16:19, Matthew W Nash a écrit : > >> Hi all, >> >> I am currently trying to read, write and append data between R and MS

Hi I am running R2.15.2 64-bit on Windows 7, using RODBC 1.3-6, MySQL5.5.20, MySQL Connector 5.5.2 - these are the latest 64-bit versions AFAIK. sqlQuery and sqlSave work fin as expected, but in a long session with a few sqlSave() calls, I get an error, for example: Error in sqlSave(channel = channel, dat = USArrests[, 1, drop = FALSE], : HY000 1461 [MySQL][ODBC 5.2(w)

Hola a todos, al intentar guardar un data.frame en formato Excel con la función: cn<- odbcConnectExcel("C:\\Documents and Settings\\ ... \\nombre.xls",readOnly=FALSE) sqlSave(cn,datos,rownames=TRUE,append=FALSE,safer=FALSE) close(cn) me da el siguiente error: Error en sqlSave(cn, datos, rownames = TRUE, append = FALSE, safer = FALSE) : [RODBC] Failed exec in Update 22018 39

Hi I am using package RODBC version 1.0-1 under R version 1.7.1 on Windows XP Pro. I am having problems writing a new table to an (Excel) database using sqlSave. I connect to an empty Excel spreadsheet using odbcConnectExcel (which, I believe, uses the Microsoft Excel Driver DSN). Then I try and save a new table to the database(spreadsheet) using SqlSave, but obtain an error message. Below is

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