Results 1 to 7 of 7
  1. #1
    New Lounger
    Join Date
    Jan 2002
    Location
    Black Earth, Wisconsin, USA
    Posts
    22
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Read Only (Access 97)

    This database is on a network. Whenever we try to export/save as a pop up menu comes up saying it is Read Only. We have researched and no one else is attempting to use or is using the database. Any ideas on why the "READ ONLY" comes up and does not allow us to export/save as? <img src=/S/surrender.gif border=0 alt=surrender width=31 height=23>

  2. #2
    Gold Lounger
    Join Date
    Feb 2001
    Location
    Sint Niklaas, Belgium
    Posts
    2,778
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Read Only (Access 97)

    Two possible causes:
    Do you have full permissions to the directory where the mdb is ? Or only read permission?
    If the mdb have being copied to the directory from a cd-rom, it may have the read-only attribute set. Check in the properties of the file in windows explorer.
    Francois

  3. #3
    New Lounger
    Join Date
    Jan 2002
    Location
    Black Earth, Wisconsin, USA
    Posts
    22
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Read Only (Access 97)

    The access rights are OK. This is a database that has been used successfully over the past year. In the last couple of months is when problems started. The information that is being exported is over the 16,000 row limit of Excel. I'm not sure if the problem started when the rows got to that limit or before. I'm not a programmer just a self taught user. They have asked for my help because I've more experience with Access than anyone else in the facility. We have been trying to figure out new ways of exporting the data. Any help is appreciated. <img src=/S/butterfly.gif border=0 alt=butterfly width=15 height=15>

  4. #4
    Gold Lounger
    Join Date
    Feb 2001
    Location
    Sint Niklaas, Belgium
    Posts
    2,778
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Read Only (Access 97)

    If you export out of the database, it doesn't matter the database is read-only or not. I just test it, opening the Northwind.mdb from the cd-rom and I can export. I also tested to export a table with 29376 rows to Excel 97. No Problem. From another thread, I remember somebody saying the limit was about 65000 rows.
    Have you tried to export to another format (csv or txt) ?
    Francois

  5. #5
    2 Star Lounger
    Join Date
    Apr 2001
    Location
    Wellington, New Zealand
    Posts
    173
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Read Only (Access 97)

    When you say "it is 'Read Only'", what do you mean by 'it' (the database or the export file directory).

    If the error happening when you are trying to export the file, it could be the permissions on the directory that you are trying to export to. Make sure there are no denies on the directory for individuals or groups that may be 'superceding' any grants.

  6. #6
    New Lounger
    Join Date
    Jan 2002
    Location
    Black Earth, Wisconsin, USA
    Posts
    22
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Read Only (Access 97)

    We are trying to export a 16,000+ query to Excel. We go through the steps and it looks like it is going to export when a pop up window comes up. I have attached a Word document with a print screen of the pop up box.
    Attached Files Attached Files

  7. #7
    3 Star Lounger
    Join Date
    Jan 2001
    Location
    Edmonton, Alberta, Canada
    Posts
    326
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Read Only (Access 97)

    I have occasionally run into that in the past when exporting (it's not complaining about your database, it's complaining about the "object" you're exporting to). Try exporting to a different directory, and if that works, you can then use Windows to move the Excel file into the correct directory.

    Never did have it happen often enough to narrow down my problems (except that being read only had nothing to do with it), but I suspected the length of the path had something to do with it.

    I haven't seen the problem (yet) in Access 2000.

Posting Permissions

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