Results 1 to 3 of 3
  1. #1
    5 Star Lounger
    Join Date
    Jan 2001
    Location
    austin, Texas, USA
    Posts
    1,029
    Thanks
    0
    Thanked 0 Times in 0 Posts
    when i try to do this:

    DoCmd.TransferText acExportDelim, "", "RUGItemChangeTable", FilePath & "MLRA\MLRA_Changes.xls", True, ""

    i get the error "Database or Object is read-only"

    I can get the data out using

    DoCmd.OutputTo acTable, "RUGItemChangeTable", "MicrosoftExcelBiff8(*.xls)", FilePath & "MLRA\MLRA_Changes.xls", False, "", 0

    in other news, this works:

    DoCmd.TransferText acExportDelim, , "EditMDS", FilePath & "MLRA\MLRA.txt", True

    Weird! I'd like to use transfer text as there is a (somewhat remote) chance that the data could exceed the row amount in Excel (2003).

  2. #2
    Gold Lounger
    Join Date
    Jun 2001
    Location
    Crystal Beach, FL, Florida, USA
    Posts
    3,436
    Thanks
    1
    Thanked 34 Times in 34 Posts
    Quote Originally Posted by steve_skelton13 View Post
    when i try to do this:

    DoCmd.TransferText acExportDelim, "", "RUGItemChangeTable", FilePath & "MLRA\MLRA_Changes.xls", True, ""

    i get the error "Database or Object is read-only"

    I can get the data out using

    DoCmd.OutputTo acTable, "RUGItemChangeTable", "MicrosoftExcelBiff8(*.xls)", FilePath & "MLRA\MLRA_Changes.xls", False, "", 0

    in other news, this works:

    DoCmd.TransferText acExportDelim, , "EditMDS", FilePath & "MLRA\MLRA.txt", True

    Weird! I'd like to use transfer text as there is a (somewhat remote) chance that the data could exceed the row amount in Excel (2003).
    I noticed that aside form trying to export different tables, the 2 "TransferText" lines have another difference! The 2nd option (the "Specification Name" is "" in the first instance, and Null in the 2nd.
    Mark Liquorman
    See my website for Tips & Downloads and for my Liquorman Utilities.

  3. #3
    5 Star Lounger
    Join Date
    Jan 2001
    Location
    austin, Texas, USA
    Posts
    1,029
    Thanks
    0
    Thanked 0 Times in 0 Posts
    that's true but i've been using the same syntax as the second, working code. the only reason there's the empty quotes is, i copy/pasted the VB code generated from a converted macro - which works in a new, empty DB but not on the one i am using. When i write the macro on the target DB, not only doesn't it run but it won't convert to VB.

    In any case, I don't think that is the issue - the same error occurs with or without the empty quotes.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •