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

temporary tables

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

    temporary tables

    Is there a way to use/create temporary tables that only exist for the duration of a script or function and do not become part of the database?

    Or do I need to create the tables. use them and then remove them from the database using TABLE_REMOVE()?

    #2
    Re: temporary tables

    I have done that.
    Time consuming to set up.
    Found it better for me to leave them built, fillem and zapem when done.
    Dave Mason
    [email protected]
    Skype is dave.mason46

    Comment


      #3
      Re: temporary tables

      A table doesn't need to be part of the database if you reference it with the fully qualified path. Thus it is not necessary to have any tables in a database if the autoexec opens an xdialog which serves as the starting point.

      You can also add and drop tables with xbasic.
      There can be only one.

      Comment


        #4
        Re: temporary tables

        Originally posted by DaveM View Post
        I have done that.
        Time consuming to set up.
        Found it better for me to leave them built, fillem and zapem when done.
        Yea, that is what I am doing with one right now but I need to do it with about 9 more and I just did not want to leave that many temp tables in the database.

        I am looking at possibly using table.erase() as it says it removes the table and all support files which should also mean I would not even need to zap the tables.

        Comment


          #5
          Re: temporary tables

          Originally posted by Stan Mathews View Post
          A table doesn't need to be part of the database if you reference it with the fully qualified path. Thus it is not necessary to have any tables in a database if the autoexec opens an xdialog which serves as the starting point.

          You can also add and drop tables with xbasic.

          Stan,

          What I am doing is duplicating records of a set that have to do with order entry. I looked at other topics on that subject and found the suggested methods too cumbersome. Duplicating the parent and then using temp tables to recreate the one-to-many child records is simple and fast but it requires creating temp tables to copy the records to and then update the id linking field.

          For one set it would be one parent and 5 child so that means 5 temp tables that I really do not want to just leave hanging around in the db.

          Comment


            #6
            Re: temporary tables

            This works and does not require leaving the table and then zapping it to clear it out for the next use.

            Code:
            temp_db_name = filename_decode("[PathAlias.ADB_Path]\temp.dbf")
            table.erase(temp_db_name, .t.)

            Comment


              #7
              Re: temporary tables

              I do the same thing for a car deal with main and children
              I use the appropriate information in fields from 7 diff tables and put the info into 1 temp table to be able to print a bank contract with no breaks in it that alpha report writer can't do. Then I use Crystal Reports to print the 26"-36" contracts.
              after the print, the temp table is emptied.
              Dave Mason
              [email protected]
              Skype is dave.mason46

              Comment


                #8
                Re: temporary tables

                Hi Dave,
                Wouldn't a mapped table accomplish the same goal?
                Robin

                Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

                Comment

                Working...
                X