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

When to use table.open_session()

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

    When to use table.open_session()

    Lets say I have a form that displays data from a set of 1 to many of customer to transactions and I have a button calling a function that opens a new copy of the transactions file to loop through all the transactions and does some type of totaling or whatever. In the function should I just use table.open() or should I use table.open_session()? Does it make a difference is I am just reading or reading and writing to the file?

    Thanks,
    Jeff Ryder

    #2
    Re: When to use table.open_session()

    loop through all the transactions and does some type of totaling or whatever
    Don't need to open a table to get totals, etc.

    tablesum() and dbsum() will extract that info.
    There can be only one.

    Comment


      #3
      Re: When to use table.open_session()

      Thanks Stan, the code is more complicated then just a simple total. In the code below should I use table.open_session("artransaction") or table.open("artransaction"). This function is called from a form that is associated to a set that includes arcustomer and artranaction with the transactions displaying in an embedded browse. This in my simplest function. I have several functions for other forms that I open a table that is already open on the form.

      Code:
      'Date Created: 20-Feb-2009 04:14:09 PM
      'Last Updated: 04-May-2009 02:04:53 PM
      'Created By  : Jeff
      'Updated By  : Jeff
      FUNCTION GetCustomerAging as V (vAdate as d, byref vrCurrent as n, byref vrOver30 as n, byref vrOver60 as n, byref vrOver90 as n, byref vrOver120 as n)
      	dim vCptr as p = table.get("arcustomer")
      	dim vTptr as p = table.open("artransaction",FILE_RO_SHARED)
      	dim vQptr as p
      	dim vID as n
      	dim vAgiang as p
      	dim vAge as n
      	
      	vId = vCptr.id
      	
      	'create query of all non-paid transactions
      	Query.Order=""
      	Query.Filter="customerid = VAR->vID .and. status != \"PD\""
      	Query.Options=""
      	vQptr=vTptr.query_create()
      	
      	'initialize counts
      	vrCurrent=0
      	vrOver30=0
      	vrOver60=0
      	vrOver90=0
      	vrOver120=0
      	
      	'total up customer aging
      	vTptr.fetch_first()
      	WHILE .not. vTptr.fetch_eof()
      		if vTptr.type != "P" then
         			vAge=vAdate - vTptr.duedate
         		else
         			vAge=0
         		end if
      		SELECT
      			CASE vAge > 120
      				vrOver120 = vrOver120 + vTptr.balance
      			CASE vAge > 90 .and. vAge <= 120
      				vrOver90 = vrOver90 + vTptr.balance
      			CASE vAge > 60 .and. vAge <= 90
      				vrOver60 = vrOver60 + vTptr.balance
      			CASE vAge > 30 .and. vAge <= 60
      				vrOver30 = vrOver30 + vTptr.balance
      			CASE else
      				vrCurrent = vrCurrent + vTptr.balance
      		END SELECT
      		vTptr.fetch_next()
      	END WHILE
      	
      	vQptr.drop()
      	vTptr.close()
      END FUNCTION
      Jeff Ryder

      Comment


        #4
        Re: When to use table.open_session()

        I'm not sure what you should do but I can tell you how I do it and have been doing it for years - long before open_session() was available (hint, hint).

        I just use table.open(). If I need to have it open twice, I simply assign a different pointer to it:
        tp1 = table.open("MyTable")
        tp2 = table.open("MyTable")

        For example, in at least one case I was using tp1 to enter new records while using tp2 to run some type of search. (I don't recall the details so don't ask why.)

        I've done this a few times and never had an issue. Consequently, I have no idea why there is a need for open_session(). There probably is a need for it but I haven't been able to figure out what that is. Perhaps if I was looking at records in both tables (rather than entering in one and looking in the other) it would be needed. Or, maybe it has something to do with active link tables???

        Comment


          #5
          Re: When to use table.open_session()

          Cal, Thanks for your input. I have not seen problems with what I have been doing so I will leave it for now. "Don't fix what is not broken."
          Jeff Ryder

          Comment

          Working...
          X