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

DDE Error Message on V7 Runtime with a5.close() method...

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

    DDE Error Message on V7 Runtime with a5.close() method...

    Aaron or Lenny;

    Any idea what's causing this error message? It was fine before the A5V7 3004 Build update. This error occurs when I use the a5.close() command on my applications 5-7 times out of 10.

    This occurs when I use the A5V7 Runtime. No errors happen when I use the A5V6 Runtime.

    "DDE Server Window:Alpha5.exe - Application Error"

    "The instruction at "0x0096454a" referenced memory at "0xffffff28". The memory could not be "read". Click on OK to terminate the program."
    Last edited by awj; 11-11-2005, 12:30 AM.

    #2
    does it happen in alphasports?

    Comment


      #3
      I'll check it out tonight...

      Hi Selwyn;

      I'll check it when I get home this evening. I have it on my laptop at home. I'll notify you once I know if I get the same error message, or otherwise.

      many thx, awj

      Originally posted by Selwyn Rabins
      does it happen in alphasports?

      Comment


        #4
        Hi Selwyn;

        I can't seem to duplicate the error in AlphaSports. It's only doing it with my "bG Monitor" application when I run the A5V7 runtime. What does the DDE thing mean? Could it be some variables are still open when I exit the app, or something? I'm at a total loss on this one.

        If I run it in the A5V6 runtime, no problem.

        awj
        Last edited by awj; 11-12-2005, 07:24 PM.

        Comment


          #5
          if you can send us your app, and we are able to duplicate the problem, we will be able to figure out what's going on.

          thanks

          Comment


            #6
            App on the way...

            Thanks Selwyn;

            I'll pack it up before the end of the weekend.

            thx, awj :)

            Originally posted by Selwyn Rabins
            if you can send us your app, and we are able to duplicate the problem, we will be able to figure out what's going on.

            thanks

            Comment


              #7
              DDE Error was almost resolved... I thought....

              Hi Selwyn;

              I had installed some software last week, that seemed to do something odd, but I never gave it any thought. So, I set my PC back to the Restore Point prior to that installation.

              It appeared to be fine for a while. I now, had to reinstall the latest A5V7 patches, and it looks like the error messages are back again.

              I'll send my bG application to you before the end of the weekend.

              Thanks! awj :(
              Last edited by awj; 11-13-2005, 02:00 AM.

              Comment


                #8
                DDE Error on another desktop machine...

                Hi Selwyn;

                I tried it on my desktop computer, and whoa, got that same annoying error message! Only here it comes once in awhile, not as often as on my laptop.

                I wonder if it's another piece of software running somehow that's causing the DDE to collide? I'll be scratching my head on this one for a long time.

                My other applications don't do this so I might have to go back to the drawing board and redo some things in my "bG Monitor" application and see if that fixes it.

                thanks again, awj :)

                Comment


                  #9
                  I am getting the similar error not on every close but as the previous poster states once every 6 or 7 application exits. Can't find any rhyme or reason.

                  AWJ, how did you come along with this? Did you upload your app to Selwyn?

                  Error message box image attached.

                  Comment


                    #10
                    Almost given up..

                    Hi George;

                    I'm glad I'm not the only one with this error. I sent the app once to Selwyn, then Aaron Brown also - but they just can't seem to duplicate the error. Funny though, it's perfect if I use the A5V6 Runtime, I'm almost certain it's got to be in the A5V7 Runtime executable file. Again though, it's like chasing a needle in a haystack. I have yet to find someone really explain to me the DDE Error message or what it's likely causes are.

                    I'm hoping that some future A5V7 updates will "somehow" mysteriously resolve this annoying bug - but for now I'm going to use the A5V6 runtime with the app since I get no problems with it.

                    The nature of the message is almost telling me that 2 different applications appear to be trying to populate the exact same memory address - but then I think I'm guessing.

                    If by some chance you run into a solution and/or cause - please let me know.

                    many thx, awj

                    Originally posted by George Corder
                    I am getting the similar error not on every close but as the previous poster states once every 6 or 7 application exits. Can't find any rhyme or reason.

                    AWJ, how did you come along with this? Did you upload your app to Selwyn?

                    Error message box image attached.

                    Comment


                      #11
                      George
                      Can you send us a copy of your application. Perhaps we will be able to duplicate the problem with your app. We were not with Andrew's app.

                      Comment


                        #12
                        Persistent Error on a5.close() Command

                        I'm resubmitting this message, as it is becoming more and more prevalent when closing Alpha Five applications. I notice other users now are also getting this ERROR message as well.

                        Is anyone going to investigate this bug any further - it's really quite annoying and my customers are getting quite frustrated with the "BUG".

                        Please let me know what's being done on this, it would be greatly appreciated!

                        awj

                        Originally posted by awj
                        Aaron or Lenny;

                        Any idea what's causing this error message? It was fine before the A5V7 3004 Build update. This error occurs when I use the a5.close() command on my applications 5-7 times out of 10.

                        This occurs when I use the A5V7 Runtime. No errors happen when I use the A5V6 Runtime.

                        "DDE Server Window:Alpha5.exe - Application Error"

                        "The instruction at "0x0096454a" referenced memory at "0xffffff28". The memory could not be "read". Click on OK to terminate the program."

                        Comment


                          #13
                          They "couldn't find" any problem...

                          Hello George,

                          They looked at my app, but to no avail. I'm completely frustrated with this error as I'm sure you are. I've had lots of complaints from my customers on this.

                          I hope Alpha Software is going to dig deeper on this. It's not a good thing to have that error come up frequently. I've tried on several machines, and all do the same thing.

                          In a nutshell, it's like I'm in "Application Error" purgatory - no resolve as yet.

                          thx, awj

                          Originally posted by George Corder
                          I am getting the similar error not on every close but as the previous poster states once every 6 or 7 application exits. Can't find any rhyme or reason.

                          AWJ, how did you come along with this? Did you upload your app to Selwyn?

                          Error message box image attached.

                          Comment


                            #14
                            I have not seen this in my apps for some time now, in fact had forgotten about this post. I will resubmit any reoccurences to this thread and send Selwyn the app causing the issue.

                            Comment


                              #15
                              Originally posted by George Corder
                              I have not seen this in my apps for some time now, in fact had forgotten about this post. I will resubmit any reoccurences to this thread and send Selwyn the app causing the issue.
                              I would be curious to know if the people that are experiencing this error share a similar piece of hardware on their notebook or desktop ?

                              I vaguely remember experiencing similar issues with a specific software and the problem completely disappeared after I replaced a video card with another card........

                              Maybe post computer specs and see if their is a common hardware component.

                              Comment

                              Working...
                              X