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

Problem calling form in dialog mode

  • Filter
  • Time
  • Show
Clear All
new posts

  • Problem calling form in dialog mode

    I have code that runs on a button from a form (let's call it form A) that is comparing data from a quickbooks import with data in anothe alpha table. The code calls form B in dialog mode, hidden, then I set some fields on the form with data from the quickbooks import, and then activate the form and then show it, because I need the user to process form B before continuing with the script on form A. The script on form A is actually a while loop, that goes back and gets the next record from the import table.
    I noticed that form B was not actually being closed by the "close" command on form B's "close" button, although the script on form A does continue when you return from form B.
    After investigation, I found this thread on the message board, talking about the same issue. It was pointed out that you had to close form B a 'second" time, in the code on the calling form (A), otherwise form B was still in memory. Still not quite sure why that is, but none the less I added code to form A as suggested in the thread, to close form B, in the script on form A where it resumes once you return from form B, and that closes the form successfully.
    So far so good. But the problem is, when I call form B again from my "while" loop, to process the next record from the import table, it does not open properly - I open the form again, using completely standard code for opening a form in dialog mode, but the pointer to the form object is blank.

    I won't have time to develop a postable version of the code until the weekend, but I wondered if anyone could respond with any idea what is wrong.

  • #2
    Re: Problem calling form in dialog mode

    OK, attached is a test application.
    When I run the Parts Import form, and push the Check Import button, the application checks to see if the item in the import table is aready in the stock table and if not, it displays a form (enter new item) in dialog mode so I can accept the item into stock, decide not to (by using the red X), or edit it and then save it in the stock table. When the script on the "check import" button resumes, it closes the form so it is removed from memory, and then returns to check the next item.
    But when it goes to open the "enter new item" form again, something seems to be left in memory, because it opens another version of the form (enter new item0). Then as it processes each new item, it moves backward and forward between "enter new item" and "enter new item0".

    Or am I missing something really obvious?
    Attached Files


    • #3
      Re: Problem calling form in dialog mode


      I see the same in your sample. It looks like a timing issue in that the new instance is being created before the first is destroyed. I tired putting a sleep(1) but nothing changed. Not sure how this affects your process but I rearranged your code a bit so form B doesn't close. It just gets hidden by the close of the red X or the save button and then gets redisplayed. After the loop if the form test as being there it is closed.

      dim vform as P
      dim qpoint as p
      'and for the stock list
      dim stockpoint as p ("parts import") ("parts in stock")
      WHILE .not.qpoint.fetch_eof()
      	'lets see if the item is already in the stock list
      	value=stockpoint.fetch_find (indx)
      	IF value>0 THEN
      		'item already exists in stock so do nothing
      		'this is a new item so create it
      		'open a form so we can edit the info
      		If .not. is_object(vform)
      			vform = :Form.load("enter new item","dialog")
      		end if
      		'now lets enter the import item data in the form
      		'now show the form
      		'script should resume here when form
      		' is closed on the form itself
      		'close the form to remove it from memory
      	END IF
      if is_object(vform) then
      end if
      Tim Kiebert
      Eagle Creek Citrus
      A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.


      • #4
        Re: Problem calling form in dialog mode

        Thanks for the response.
        I had also tried changing the timing with sleep commands but it did not change things. It looks like something remains set up in the background even when you close the form in the script, and then clears when the script terminates, which is why it was an issue closing the form in the loop. I'll report it as a probable bug anyway.
        I tried your suggestion, avoiding the form close in the loop, and it worked perfectly. Thanks.