Results 1 to 4 of 4
  1. #1
    New Lounger
    Join Date
    Nov 2001
    Location
    Twickenham, UK
    Posts
    19
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Path Length Restrictions (Access 97)

    Does anybody know of any restrictions with regards the maximum path length when exporting tables?

    I have numerous multi-user apps which use a variety of methods for exporting data.

    Some have the path and filename 'hardcoded' in eg:
    strBackupFile = "S:CCardEFT30req" & Format(Now(), "YYYYMMDDhhmmss") & ".txt"
    DoCmd.TransferText acExportDelim, strSpec, strTableName, strBackupFile
    while others make use of the Windows Common Dialog box.
    These have all been working fine for months, but someone has recently decided to restructure the directories. <img src=/S/bif.gif border=0 alt=bif width=70 height=28>
    The resulting path names are ridiculously long (7 subdirectories, totalling over 85 characters before the file name, in one case) and I've started getting errors on the exports.

    The error is "Can't update. Database or object is read-only. (Error 3027)", when I know I have full rights to everything (I can happily create/delete/move files in the relevant sub-directories and the database is shared with no-one else in it).
    I get the same error if I try using the 'right-click, Save As/Export' route in the database window.

    The only conclusion I can come up with is that there is a restriction on the maximum path length (or number of steps down the tree)??? <img src=/S/hairout.gif border=0 alt=hairout width=31 height=23>

    Am I barking up the wrong tree? Any ideas/comments? <img src=/S/surrender.gif border=0 alt=surrender width=31 height=23>

    BTW, we have a mix of Novell and NT servers (if that makes any difference).

  2. #2
    5 Star Lounger
    Join Date
    Jan 2001
    Location
    Newbury, Berkshire, England
    Posts
    712
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Path Length Restrictions (Access 97)

    What about setting up a small test on a stand alone PC? You could see if you can find the limiting length of the path names. This would then indicate if the problem was in fact the length of the path names or related to permissions.

  3. #3
    Star Lounger
    Join Date
    Aug 2001
    Location
    Seattle, Washington, USA
    Posts
    50
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Path Length Restrictions (Access 97)

    I seem to recall Access 97 having a problem with spaces in the long file names. Could that be going on here?

    Even if not, Rupert's got a great idea.

    Tom

  4. #4
    New Lounger
    Join Date
    Nov 2001
    Location
    Twickenham, UK
    Posts
    19
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Re: Path Length Restrictions (Access 97)

    Thanks chaps,

    I'll try recreating this at home this evening (I'll set up a long path and try it with and without spaces) and see if I can replicate the problem.

    Cheers

Posting Permissions

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