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

Remote debug

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

  • Catalin
    replied
    Re: Remote debug

    Hi,
    With prerelease Build 1932-4245 25-Jan-2014 11:31 AM the problem has been solved. Two days of work lost. Thank you very much to all for the support you have given me.

    Leave a comment:


  • Catalin
    replied
    Re: Remote debug

    I have 1922 build on server and local. I have tried everything you have told me.
    I will wait for a new release if I have no choice.
    Thank you very much to all.

    Leave a comment:


  • Davidk
    replied
    Re: Remote debug

    Yes... that's it exactly Jaime. I hadn't read that post so it didn't twig. Your description of the problem and how to reproduce it was perfect.

    Leave a comment:


  • WindForce
    replied
    Re: Remote debug

    David
    Is the issue similar to what i stated here http://msgboard.alphasoftware.com/al...y-when-editing ?

    Thanks
    Jaime

    Leave a comment:


  • Davidk
    replied
    Re: Remote debug

    There was an issue with the UX/Server-Side/Save data stuff when used with a Repeating Section. I'm getting an error in the code while stepping through debug when debug is place BEFORE the ExecuteServerSideAction. It's odd that you're not getting the error... you should be. In my case the issue was present in the 1912 build... I'm not sure how far back it went. The issue has been corrected and will in tomorrow's pre-release build. Install the new pre-release tomorrow and give it another try. I'll do the same.

    Leave a comment:


  • Catalin
    replied
    Re: Remote debug

    Hi Frank,
    I upgrade the server, I made the the dialog dirty and I save it and finnaly republish it. The result is the same, nothing happens. I click the Save button and nothing happens.
    3.png

    Leave a comment:


  • Clipper87
    replied
    Re: Remote debug

    Did you upgrade your server as well ? Did you make your UX dirty & save it in that new build + publish it ?

    Leave a comment:


  • Catalin
    replied
    Re: Remote debug

    David - No, of course. Using Live Preview I can debug (step,trace) and inspect all sql args and the result is ok.

    Chris - The local database is copy of server database.

    Frank - I update the local version to build 1922, system addins build 4245 and I see no difference. I have no error on the firebug console.

    Leave a comment:


  • Davidk
    replied
    Re: Remote debug

    Catalin,

    You've got a debug statement in your server-side event... before the action. Using Live Preview, as you're stepping through the code, using Step, are you getting any errors?

    Leave a comment:


  • Clipper87
    replied
    Re: Remote debug

    your builds are different. Update your developer copy to match your server of update both to the most recent (pre) release. Next edit your component (make it dirty), save & publish again.

    If Firebug is launched within Firefox simply click on the console tab and select all or errors then see what appears out there.

    Leave a comment:


  • Catalin
    replied
    Re: Remote debug

    David, now my code is:

    debug(1)

    'To edit this action, place insertion point anywhere in the command, then click the 'Action Scripting' button'.
    ExecuteServerSideAction("Save Data::Save_Submitted_Data_to_Table_s_Impozit")

    if rtc.flagRecordWasSaved = .t. then
    dim js as C
    js = <<%txt%
    var po = {dialog.object}.getParentObject();
    if(po)
    {
    po.setValue('A0_CPP_IMP:1', {dialog.Object}.getValue('IMPOZITCALCULAT:1'));
    po.setValue('A1_CPP_IMP:1', {dialog.Object}.getValue('IMPOZITCALCULAT:2'));
    po.setValue('A2_CPP_IMP:1', {dialog.Object}.getValue('IMPOZITCALCULAT:3'));
    po.setValue('A3_CPP_IMP:1', {dialog.Object}.getValue('IMPOZITCALCULAT:4'));
    po.setValue('A4_CPP_IMP:1', {dialog.Object}.getValue('IMPOZITCALCULAT:5'));
    po.setValue('A5_CPP_IMP:1', {dialog.Object}.getValue('IMPOZITCALCULAT:6'));

    po.setValue('A1_T1_CPP_IMP:1', {dialog.Object}.getValue('TRIM1_IC:2'));
    po.setValue('A1_T2_CPP_IMP:1', {dialog.Object}.getValue('TRIM2_IC:2'));
    po.setValue('A1_T3_CPP_IMP:1', {dialog.Object}.getValue('TRIM3_IC:2'));
    po.setValue('A1_T4_CPP_IMP:1', {dialog.Object}.getValue('TRIM4_IC:2'));

    po.setValue('A2_T1_CPP_IMP:1', {dialog.Object}.getValue('TRIM1_IC:3'));
    po.setValue('A2_T2_CPP_IMP:1', {dialog.Object}.getValue('TRIM2_IC:3'));
    po.setValue('A2_T3_CPP_IMP:1', {dialog.Object}.getValue('TRIM3_IC:3'));
    po.setValue('A2_T4_CPP_IMP:1', {dialog.Object}.getValue('TRIM4_IC:3'));
    }
    %txt%
    e.javascript = e.javascript + crlf() + js
    e.javascript = e.javascript + crlf() + "var ele = $('Impozit_societati');" + crlf() + "{dialog.object}.closeContainerWindow(ele);"
    else
    e.javascript = "alert('" + rtc.errorText + "');"
    end if

    and still not working.

    Frank - my server version is Alpha Anywhere Build 1900-4243
    and my local version 12.2 build 1856, System addins 4237
    1.png
    2.png
    I don't know to use firebug. I use it only to inspect control names. But running the app with firebug does not fire any message and does not working.
    Last edited by Catalin; 01-21-2014, 05:44 PM.

    Leave a comment:


  • christappan
    replied
    Re: Remote debug

    Well, and make sure the database tables on the server match those on your development machine.

    Leave a comment:


  • Clipper87
    replied
    Re: Remote debug

    Also check if you are running the same version of web application server & developer; they need to be the same build. Otherwise I stick to my suggestion to use Firebug to see if anything pops up there in the console.

    Leave a comment:


  • Davidk
    replied
    Re: Remote debug

    I'm going to try your code in my UX... but... on first glance I think there's a problem with your use of e.javascript. Do you have this code running after your ExecuteServerSideAction? If so then, I think, you're wiping out that action by first setting e.javascript to "". And... again with e.javascript = js.

    The ExecuteServerSideAction sets e.javacript... so that's sacred. I would think the end of your code should be...

    Code:
    e.javascript = e.javascript + crlf() + js
    e.javascript = e.javascript + crlf() + "var ele = $('Impozit_societati');" + crlf() + "{dialog.object}.closeContainerWindow(ele);"
    else
    e.javascript = "alert('" + rtc.errorText + "');"
    end if
    Going to try it now.

    Leave a comment:


  • Catalin
    replied
    Re: Remote debug

    Hi Frank,
    Is a web application. I'm sorry to confuse you I meant "working preview". As I was saying in working preview the app save the data and close the dialog. In live preview is working good too. Only running on the web server does not work.

    Catalin

    Leave a comment:

Working...
X