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

Debug.log

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

    Debug.log

    I keep getting a 0 byte debug.log file showing up on my desktop when working with the developer.

    Does anyone know where this is coming from or, more importantly, how I can turn it off?
    Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

    #2
    Re: Debug.log

    Are you running a pre-release ?
    Frank

    Tell me and I'll forget; show me and I may remember; involve me and I'll understand

    Comment


      #3
      Re: Debug.log

      Originally posted by iRadiate View Post
      I keep getting a 0 byte debug.log file showing up on my desktop when working with the developer.

      Does anyone know where this is coming from or, more importantly, how I can turn it off?
      I get the same thing. I've been just ignoring it and haven't bothered to say anything until I saw your post.

      I'm not running a pre-release by the way. I'm still on the 2446_4365 build from 10/01
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Programmatic-Technologies.com
      Independent Developer & Consultant​​

      Comment


        #4
        Re: Debug.log

        I'm not running a pre-release. It's happening with the latest official release too.
        I've noticed the file is created as soon as the Alpha Development application is opened.
        Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

        Comment


          #5
          Re: Debug.log

          This, (0 byte debug.log), has recently started popping up on my desktop with my Alpha Anywhere since I upgraded to Windows 10.
          If I delete it, it simply reappears after doing nothing more than opening and closing Alpha Anywhere v3.11 (version 12.3, Build 2689 - Sys Addins: Build 4440).
          It's simply a pain in the butt when software inexplicably does its own thing.
          Is there no answer?

          Comment


            #6
            Re: Debug.log

            I reported as a bug well over a year ago and Alpha fixed it at that time, I can't remember the build version, but I haven't seen it since.

            If I recall correctly, it had something to do with opening Alpha Developer from a desktop shortcut. Opening it directly from alpha.exe seemed to not generate the debug.log file.
            But, as I say I haven't seen it since. You have an old build so you might want to update it.
            Last edited by iRadiate; 10-02-2016, 08:03 PM.
            Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

            Comment


              #7
              Re: Debug.log

              Originally posted by fwala View Post
              Is there no answer?
              Update to the latest version of Alpha if you can.
              Mike Brown - Contact Me
              Programmatic Technologies, LLC
              Programmatic-Technologies.com
              Independent Developer & Consultant​​

              Comment


                #8
                Re: Debug.log

                Frank Wala,
                I too am using Build 2689 for production. Be very careful if you update to newer version. This is my second attempt at updating to a newer version. First I tried Build 2999, sometime ago and some things failed. Now I am trying Build 3670, things still fail. I have a UX that simply refuses to "submit" its data to the server with the standard "submit" button. I may be forced to scrap the server-side Action Scripting that saves the checkbox control on that form to the WebSecurityMembers table since that code cannot be moved to different server embed point. My own code can be placed in a generic ajax callback, I don't think the UX will refuse to call my own callback.

                Comment


                  #9
                  Re: Debug.log

                  Thanks for all the input. Turning off the development server prompt at startup seems to have resolved the problem.

                  My system is for 1 user only - me. I wrote it over 25 years ago with Alpha4. I've only spent (unnecessary) monies on upgrades due to keeping up with changing technologies. Who's running Windows 3.1? I'm not about to drop a grand on software I really can't benefit from - I don't use servers or have any mobile apps. Seems Alpha has trended for big business clients as well as big bucks. The home user like myself is left on the outside looking in.
                  Thanks again for your diligence.

                  Comment

                  Working...
                  X