Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

SYSTEM CANNOT FIND THE SPECIFIED PATH

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    SYSTEM CANNOT FIND THE SPECIFIED PATH

    I created an application that has a set with 4 child databases attached. (One database is a one to many link, the others are just one to one.) The child databases are in different folders on the M: network drive.

    When I try to call up the data entry form from the main menu of my application on a machine that has the A5 runtime loaded i get, "The system cannot find the path specified. >" If I execute the same exact application on my PC (which has the runtime and full versions), i don't get the error. (Everything works fine.)

    I checked and rechecked the path. I can actually browse out to the m: drive (where the databases are located) and can see the .dbf's just fine. I recreated the set thinking a link in there was messed up. That still didn't work. I thought maybe there was an NT permissions problem on the folders, so i logged on as myself (administrator) to a machine with just the runtime version....that didn't work either. (I also double checked the permissions on the folders. They're set to EVERYONE having full control.) I've tried everything I can think of.

    Any ideas?

    #2
    RE: SYSTEM CANNOT FIND THE SPECIFIED PATH

    I'm assuming that your app works properly on your computer because it is looking for the tables (DBF's) on your hard drive and NOT the file server. If this is the case, it sounds like the app is looking for the data-entry form based on the drive and path of the form's table on your computer. When it gets to the network, it still thinks that that table is on your drive (C:) instead of the M: drive. This can happen when the path for each table in the set is different.

    My first suggestion would be to keep your application's data and support files (all tables, *.DD* files, *.SE* files, etc.) in the same folder (I usually put my program files in one folder, and the data and support files in a sub-folder of that one). This way, all the tables in the set are in the same location, so the app doesn't have to look for a different path.

    For more information, check out Steve Working's tip #23 on this issue (click on the Alpha logo at the top of the message board screen, then click on Tips, and the Search for a Tip).

    Comment


      #3
      RE: SYSTEM CANNOT FIND THE SPECIFIED PATH

      I thought about keeping my tables in the same folder....however, some of these tables get used in other applications. That's why I have them in a "centralized location" on the file server under it's own folder.

      Is it that it's impossible to have databases in different folders? Or is it just recommended to help speed things up?

      I double checked my paths and it's looking to the M: drive for all database files. I also checked my C: drive for the main child database name. It couldn't find it. As far as I know, the dbf files only exist on the M: drive.

      Comment


        #4
        RE: SYSTEM CANNOT FIND THE SPECIFIED PATH

        Scott,

        I think Bill is on target.

        If your database contains tables that are scattered across several folders Alpha Five will embed the actual path to each table inside the datadictionary files for the database itself. This happens when you introduce each table to the database dictionary by 'adding' the table to the database.

        If you move the database to another folder or to a different workstation and then try to open it, Alpha Five consults its internal dictionary files for the database and tries to open each table using the embedded pathing information that you supplied when you 'added' each table to the database.

        On the other hand, if all of your database components are located in the same folder to begin with, Alpha Five does not seem to embed any 'pathing' information in its database dictionary. In the absence of an embedded path, Alpha Five assumes that all tables will be in the same folder as the database files themselves. This makes the database 'portable'. As long as the database files (the "*.A*" series files) and all the tables, indexes, and memo files, with all related dictionary files are kept in a single folder on the development machine, you can move the entire database to another folder or to another machine without encountering path problems.

        So, IMHO you have 2 choices:

        1) Spread your tables across multiple folders on the development machine, and then carefully recreate exactly the same path structures on each target machine to which you want to move the database... Drives and foldernames will have to match.

        0r

        2) Keep it simple, and put everything in one folder.

        -- tom

        Comment


          #5
          RE: SYSTEM CANNOT FIND THE SPECIFIED PATH

          Thanks for all the suggestions. Here's what I had to do to get this to work:

          1. On the client PC, delete the shadowed database that you're having the problem with.
          2. On the developer PC (which contains the full version of A5), open the set and recreate each link.
          3. Go back to the client PC re-run the Network Optimize option.

          That seemed to fix my problem.

          Comment

          Working...
          X