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



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

All tables in app in same folder?

  • Filter
  • Time
  • Show
Clear All
new posts

  • All tables in app in same folder?

    I have two databases in two different folders. One is my Customer Activity database. One is my Stove Models and Products database.

    Originally I was developing these as separate applications but am now considering merging them into the same application.

    I like the idea of having them as separate databases but now I want to share the data from the Products database with my Customer Activity application to create estimates and keep these estimates in a table with the Customer Activity application.

    I am wondering which way is best. Should I merge the two folders and copy all files from each database application into the same folder and then continue developing my applications using only this one folder? Or, can I just keep the two folders as they are and add the tables I want to use from the Products database into my Customer Activity application?

    Seems to me I got some warnings about adding databases from foreign folders when I've played with this before. What are the disadvantages to keeping the databases in two separate folders? If I want to have both a small Products application and the more complex Customer Activity application won't it be best to keep the simple Products databases in their own folder? If I want to copy the Products application I can copy it's folder. If I put it all in the same folder I will have to copy a lot of files I won't need for that simple application.

    I suppose I should just charge ahead and see what happens. I am inclined to leave the databases in two separate folders and add the needed tables to each application as needed. But I don't want to make a mistake in design that I will have to redo later, when I learn more about what the heck I am doing.

    Anybody have any tips on how I should do this?

    Sean Kennedy

    (part time developer, full time business person)

  • #2
    Re: All tables in app in same folder?

    If all tables are in the same directory, then the application will work correctly even if the directory is changed. This can happen if you move the application to a server from a local drive, make another copy for testing purposes, etc.

    The problem with having a single database with tables in multiple directories is that Alpha must store complete paths in set definitions, operations, etc.

    Your appliation will work, it is just not portable to different locations.



    • #3
      Re: All tables in app in same folder?

      If you combine the two dbs in one folder, you may need to correct certain hardcoded path references - e.g. table lookups in field rules - if you had been cross-referencing dbs.

      If you really want to keep the dbs in their own folders and make them portable, put both folders under another, such as "db_data". That way you can transport db_data to another machine w/o breaking anything.
      AlphaBase Solutions, LLC


      • #4
        Re: All tables in app in same folder?

        Originally posted by Peter.Greulich View Post
        If you combine the two dbs in one folder, you may need to correct certain hardcoded path references - e.g. table lookups in field rules - if you had been cross-referencing dbs.

        If you really want to keep the dbs in their own folders and make them portable, put both folders under another, such as "db_data". That way you can transport db_data to another machine w/o breaking anything.
        I think that's what I will do. I'll keep application in it's each folder but place them both inside another folder.

        Is that why A5 gives the warning? So that if the folder gets copied to another computer the relative paths will remain intact? That seems simple enough to control. Is there any other reason why I shouldn't keep the tables in another folder?

        What if I were to access the same tables from two different applications at the same time? Will that cause problems?

        I guess I shouldn't be obsessed with this and just get on with it. But I'm not really a developer. I just want to use this for my business and I don't want to start with a bad design if I can avoid it.