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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Storing a pointer in the e._state object

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    Storing a pointer in the e._state object

    I have written a reusable dialog report interface to handle the over one hundred reports I need to eventually write. I am using a single Action Javascript “Open Report, Label or Letter Layout” method to open any report and have converted it to text mode. I am using a UDF Javascript function inside this code to set all of the report object (ro) variables. I am initializing the “ro” object on the server-side and storing the object in the e._state variable which gets passed to the client-side. I am creating a single “ro” pointer (dim e._state.ro as p) and then dimming 16 member variables of character type to the “ro” pointer.

    This is the server-side code that initializes the “ro” object:

    Code:
    ' Setup the report object member variables
dim e._state.ro as p
dim e._state.ro.reportName as c = e.arguments.Find("ReportName").data + "@” + database + “.alb"
dim e._state.ro.reportNameShort as c = e.arguments.Find("ReportName").data
dim e._state.ro.download as c = download
dim e._state.ro.xbasicFunction as c ‘ not used at this time
dim e._state.ro.clientSideFilename as c ' not used at this time
dim e._state.ro.reportMessagesDivId as c = "RI_ReportArea"
dim e._state.ro.filter as c ' not used at this time
dim e._state.ro.order as c ' not used at this time
dim e._state.ro.sqlFilter as c = request.variables.V.R1.filter_definition
dim e._state.ro.sqlOrder as c = request.variables.V.R1.order_definition
dim e._state.ro.arguments as c = e.RI_Args + "aReportTitle|Character|" + request.variables.V.R1.report_title
dim e._state.ro.workingMessage as c = "Printing report: " + e._state.ro.reportNameShort
dim e._state.ro.pdfoptions as c = pdfOptions 
dim e._state.ro.displayMode as c ‘ not used at this time
dim e._state.ro.saveAs as c = "pdf"
dim e._state.ro.pdfOpenParameters as c = pdfOpenParameters
    This is the client-side function which sets up the A5 report object:

    Code:
    function RI_BeforeExecuteOpenReport(ro)
{
   if (typeof {dialog.object}.stateInfo.ro.reportName != 'undefined') ro.reportName = {dialog.object}.stateInfo.ro.reportName;
   if (typeof {dialog.object}.stateInfo.ro.reportNameShort != 'undefined') ro.reportNameShort =    {dialog.object}.stateInfo.ro.reportNameShort;
   if (typeof {dialog.object}.stateInfo.ro.download != 'undefined') ro.download = {dialog.object}.stateInfo.ro.download;
   if (typeof {dialog.object}.stateInfo.ro.xbasicFunction != 'undefined') ro.xbasicFunction = {dialog.object}.stateInfo.ro.xbasicFunction;
   if (typeof {dialog.object}.stateInfo.ro.clientSideFilename != 'undefined') ro.clientSideFilename = {dialog.object}.stateInfo.ro.clientSideFilename;
   if (typeof {dialog.object}.stateInfo.ro.reportMessagesDivId != 'undefined') ro.reportMessagesDivId = {dialog.object}.stateInfo.ro.reportMessagesDivId;
   if (typeof {dialog.object}.stateInfo.ro.filter != 'undefined') ro.filter = {dialog.object}.stateInfo.ro.filter;
   if (typeof {dialog.object}.stateInfo.ro.order != 'undefined') ro.order = {dialog.object}.stateInfo.ro.order;
   if (typeof {dialog.object}.stateInfo.ro.sqlFilter != 'undefined') ro.sqlFilter = {dialog.object}.stateInfo.ro.sqlFilter;
   if (typeof {dialog.object}.stateInfo.ro.sqlOrder != 'undefined') ro.sqlOrder = {dialog.object}.stateInfo.ro.sqlOrder;
   if (typeof {dialog.object}.stateInfo.ro.arguments != 'undefined') ro.arguments = {dialog.object}.stateInfo.ro.arguments;
   if (typeof {dialog.object}.stateInfo.ro.workingMessage != 'undefined') ro.workingMessage = {dialog.object}.stateInfo.ro.workingMessage;
   if (typeof {dialog.object}.stateInfo.ro.pdfoptions != 'undefined') ro.pdfoptions = {dialog.object}.stateInfo.ro.pdfoptions;
   if (typeof {dialog.object}.stateInfo.ro.displayMode != 'undefined') ro.displayMode = {dialog.object}.stateInfo.ro.displayMode;
   if (typeof {dialog.object}.stateInfo.ro.saveAs != 'undefined') ro.saveAs = {dialog.object}.stateInfo.ro.saveAs;
   if (typeof {dialog.object}.stateInfo.ro.pdfOpenParameters != 'undefined') ro.pdfOpenParameters = {dialog.object}.stateInfo.ro.pdfOpenParameters;

// The stateInfo.ro object must be deleted to clear out the old values, otherwise they “stick”.
   delete {dialog.object}.stateInfo.ro;

}
    I have to delete the “ro” object on the client-side in order to remove all of the variables for the next time a report is run. If I don’t, the values I initially set on the server-side do not get overwritten the next time I open a report.

    I realize that some of the data I am passing in the e._state variable already exists in the dialog controls and could be read directly on the client-side using {dialog.object}.getData(). The reason I am initializing everything on the server-side is because some of the data only exists on the server-side and also for future maintenance. I already know some of the data will need to be formatted differently than it exists in the controls and I will need to come back from time to time to make other tweaks and changes. I would prefer to put all of the smarts in the server-side and have the client-side be as straightforward as possible.

    It just occurred to me this morning that pointers/objects may not be allowed just like with session variables. Is it ok to create a pointer in the e._state object on the server-side? The code works fine of course in Live Preview mode. If pointers are not allowed inside the e._state object, I suppose I could store all of the data I need in character strings. Video M58 demonstrates creating a JSON object on the client-side, but does not mention anything about instantiating an object on the server-side.

    Thanks
    Last edited by DaveF; 12-19-2012, 09:13 PM.
    Tags: None
Previous template Next
Working...
X