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

Request recommendation on best table access method

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

  • Steve Workings
    replied
    Re: Request recommendation on best table access method

    Everyone will have different preferences, to be sure, and coming into all of this from Alpha Four, I understand your substantial use of .dbfs. However, I'll suggest that it's not that big a jump to just omit .dbf from what you're doing, save a bunch of work, effort, and maybe a surprise or two. Besides, if you're using SQL you're probably using Views -- might as well just work in SQL.

    Leave a comment:


  • parkjammer
    replied
    Re: Request recommendation on best table access method

    Thanks Steve.

    I just wanted to be sure there wasn't some other method people were using. I think I'll add in the active-link tables for my own "quick review" purposes but not for direct use in Alpha Five objects.

    This relates to another posting I had requesting recommended methods to handle DEV-to-PROD movement of the app (laptop to server).

    My conclusion at present is:
    1. Use DBFs for initial framing of the database (easy on-the-fly table re-design)
    2. Uprgrade to RDBMS tables as soon as database design stabilizes (SQL Server, Oracle, MySQL), preferably using tools like Navicat rather than the "Upsize Genie"
    3. Create and test connection strings for DEV and PROD and name them accordingly (e.g., MyDatabaseName_DEV, MyDatabaseName_PROD)
    4. Create a connection string called "CURRENT" to point at either DEV or PROD depending on your current focus (e.g., MyDatabaseName_CURRENT)
    5. Make sure all GRID, DIALOG, UX, and XBASIC code refers to the "CURRENT" connection string (whatever you've named it)
    6. Then... simply switch the connection-string content for the CURRENT connection string as your app migrates from DEV to PROD (or back and forth)
    7. For data review but not for Alpha objects, create active-link tables for convenience (rather than TOAD, Navicat, PHPmyadmin, etc)


    Zeroing on a finished (beta) app!

    Thanks,

    Allan

    Leave a comment:


  • Steve Workings
    replied
    Re: Request recommendation on best table access method

    Connection string to get to the SQL tables, no active-link tables at all. If you look in most of my web projects, the desktop control panel has no .dbfs at all.

    Yes, if you wrote code to work with your .dbfs, you'll have to re-write it for SQL. But better now than later when the job would just be bigger.

    Leave a comment:


  • parkjammer
    started a topic Request recommendation on best table access method

    Request recommendation on best table access method

    I began building an application in A5v11 using local DBF tables and GRID components. Recently I used the "upsize" genie to convert to a local SQL server database. This resulted in "active-link" tables.

    Multiple entries on the forum note that active-link tables are slow and have other drawbacks. So I created a connection-string and then called the tables directly from the GRIDs via connection strings.

    Unfortunately, I have found two problems with this:
    1. Access is MUCH slower using direct-connection SQL SELECT statements than with DBF or active-link structures. I have a high-end laptop with tons of memory and a solid SQL Server install. I would have expected a better response.
    2. It looks like all my record insert/update functions have to be re-written to use pure SQL


    I am beginning to work with the UX component. My two questions to the community are:
    1. What is the best and/or fastest method you are using to connect to tables from within GRIDs and/or UX components?
    2. Do you also build active-link tables in the Alpha development interface just so you can pop open tables for content review if not for actual use within GRIDs or UX-lists?


    Thanks,

    Allan
Working...
X