similar to: sqlSave, fast=F option, bug?

Displaying 20 results from an estimated 3000 matches similar to: "sqlSave, fast=F option, bug?"

2006 Dec 22
1
bug in sqlSave with fast=F option (PR#9429)
Full_Name: Paul MacManus Version: 2.3.0 OS: Windows XP Submission from: (NULL) (216.90.169.253) See also R-help thread for October 18, 2006 --------------------------- Create a dataframe and save it to a database table "test" as follows: df <- data.frame(T=1, S=10) sqlSave(channel, df, "test", rownames=F) The table now looks like T S 1 10 If I create another
2006 Mar 23
0
sqlSave
Dear Tobias, I finally succeeded in exporting my dataframes from R into Access with this script: library(RODBC) canal <- odbcConnectAccess("D:/Floristique.mdb") sqlSave(channel=canal, dat=flore, tablename="Floristique", rownames=F, safer=F, fast=F, varTypes=c(dates="Date")) odbcClose(canal) My problem in exporting my dataframe "flore" seems to
2006 Mar 18
1
The R "fork"
Hello, I would like to call a function that can take infinite time to be executed in some circumstances (which can not be easily detected). So, I would like that once the function is being executed for more than two seconds it is stopped. I have found documentation for timers but i did not found how to "kill" a function. Moreover, I would like not to change the function code (it should
2009 May 09
1
sqlSave()
Hi all: I have created a MS Access table named 'PredictedValues' through the statement below: myDB <- odbcConnectAccess("C:/Documents and Settings/Owner/Desktop/Rpond Farming.mdb",uid="admin",pwd="") sqlSave(myDB,PredictedValues,rownames=FALSE) close(myDB) But if I run the code again with new values I get the message below: Error in sqlSave(myDB,
2009 Oct 16
2
RODBC sqlSave does not append the records to a DB2 table
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
2008 Nov 25
1
Error in sqlCopy in RODBC
Hi All, I am trying to copy portions of tables from one SQL database to another, using sqlCopy in the RODBC package. RemoteChannel = connection to remote database LocalChannel = connection to local database LocalTable = table in my local database to receive data from the remote database query <- select query in SQL sqlCopy(RemoteChannel, query, "LocalTable",
2013 Apr 03
1
sqlSave writes, but only for sqlFetch
I've been having some issues with sqlSave, and I think I've found an clue that may identify the problem. In the code at http://pastebin.com/vTAKt4bL<http://pastebin.com/W6UGKep9>, I connect to a Netezza instance, make a simple table, and query it. Despite sqlSave succeeding without error, sqlQuery tells me the table doesn't exist. Also, when I query the database outside of R, I
2007 May 31
2
Import data from Access
Hi, I want to import some data from Access and I am using the following codes: testdb <- file.path("c/../db1") channel <- odbcConnect("testdb") sqlFetch(channel,"tbl",colnames = TRUE, rownames = FALSE) It comes out the error message: 1: [RODBC] ERROR: state IM002, code 0, message [Microsoft][ODBC Driver Manager] Data source name not found and no default
2011 Feb 01
1
sqlsave and mysql database with autoincremental column
Hello, I'm trying to modify my r-script to use RODBC instead of DBI/RMySQL (no more ready-to-use package for windows). I would like to copy a data.frame of 44 columns to a table of 45 columns (the 45th is an autoincremental column). With the following commands, colnames(df)<- a vector with the names of the 44 columns
2009 Jan 26
2
R crashes when using the RODBC Package
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
2012 May 29
1
RODBC, Excel, and data truncation when writing
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 <-
2007 Jul 18
0
sqlSave, ...colnames=F, using "odbcConnectExcel" .... I still get colnames in top row of exprted sheet
I am trying to save an R data.frame as an Excel sheet. I do NOT want the column names saved into row 1. I set colnames=F. However, it still seems that the colnames are saved into row 1. Is this a bug? Or am I coding incorrectly and.or misunderstanding this feature? #example code: sheet = "c:/test2.xls" temp=data.frame(matrix(data=NA,nrow=10,ncol=15)) temp[1,1] =
2011 Nov 10
1
Help: sqlSave Error
I am using sqlSave to save my data into an existing table at MS SQL Server database. Previously my code ran smoothly but all of a sudden it stopped working. Here is my code: sqlSave(con, highVol, "dbo.futuresHighVol", append=TRUE, rownames=FALSE) Error: sqlSave(con, highVol, "jrgchis.dbo.futuresHighVol", append = TRUE, : 42S01 2714 [Microsoft][ODBC SQL Server Driver][SQL
2010 Nov 25
1
RODBC
Hi, I am running the RODBC examples form the help guide. I am trying to UPDATE a table in an Access data base but I am having an error. library(RODBC) library(termstrc) path = getwd() setwd(getwd()) dbName = "data.mdb" pathdbname = paste(path,"/",dbName,sep="") accesChannel = odbcConnectAccess(pathdbname, uid = "", pwd = "")
2012 May 20
4
write.xls
Hello, All: The "writeFindFn2xls" function in the "sos" package tries to write an Excel file with 3 sheets ('PackageSum2', 'findFn', 'call'). Unfortunately, it is often unable to do this because of configuration problems that are not easy to fix. I've found 3 contributed packages that provide facilities to write Excel files with
2006 Feb 20
1
sqlSave
Hi, I am having trouble to write/create a table, which has a date field. I want to create a stock price table, which has fields of ticker, date, price. First, I created such a table in Microsoft Access with a few rows inputs. Using sqlQuery, I found that the date field was retrieved as POSIXct value. Then I made a data.frame with POSIXct as the data type for dates. However, I received the
2003 Jan 29
1
RODBC sqlSave Error
Hi, i get error after using a data.frame with subset for "sqlSave". What can i do ? It seems that lines like this in a data.frame structure are after subset deleted and cause the error ? - attr(*, "variable.labels")= Named chr "CUSID" "Welle" "Arbeitgeberfavorit1" "Aktuelle Bewerbungssituation" ... ..- attr(*, "names")=
2003 Apr 02
1
RODBC sqlSave problem.
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,
2010 May 16
1
RODBC-Error-sqlSave
Dear R-community, After repeating the sqlSave-command 3 times on a dataframe (of size 13149 rows * 5 columns) to my MS-Access database I get the following error: *Error in sqlSave(channel, eksport_transp_acc_2, "transp_acc_scenarier", : unable to append to table ‘transp_acc_scenarier’* ** This means that the first 2 savings are completed, but the third-one is somehow not. I have an
2008 Apr 30
1
+ and - in RODBC : no longer considered factors
I have a large Sweave report that reads data from a database file. Some of the columns are 1-character strings containing only +, - or NA. An example for such a table is shown below, and can be downloaded for easier testing from http://www.menne-biomed.de/uni/test.zip (For security reasons, the file is zipped) table test hp hp1 + a - + library(RODBC) channel =