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



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

Force null on numeric SQL insert

  • Filter
  • Time
  • Show
Clear All
new posts

  • Force null on numeric SQL insert

    I have an existing SQL Server table with a numeric (int) ID column that is linked via a foreign key to another table. The numeric column value can be null or a value from the other table.

    Alpha defaults zero into the field on the grid and so I wrote an XBasic handler in the "CanInsertRecord" grid event to check for zero value and replace it with either null or "" (tried both).


    DataSubmitted.INSPECTOR_ID = NULL_VALUE() or
    DataSubmitted.INSPECTOR_ID = ""

    In both cases, the INSERT fails with the with a SQL Server FK violation error. I turned on the grid update trace and I see that it is still trying to pass a zero in the SQL INSERT i.e.

    :new_inspector_id (N) 0

    After debugging I also noticed what I assume is auto-generated server-side code that does an "args.set" and calls "convert_type" on the grid value (see attachment). Maybe this is what is re-creating the zero value.

    I found a bunch of posts re numeric, zero, null, etc. - but nothing that seems to cover this. There are workarounds on the DB side but it will likely be MUCH easier to fix this on the Alpha side if that's possible.

    Any feedback greatly appreciated.



  • #2
    Re: Force null on numeric SQL insert

    A restricted INSERT statement would also work - where it only inserts columns with values. I can't see anywhere to configure that in the grid. The update command debugging shows it creating the SQL for all columns in the underlying SQL query used in the grid - regardless of whether they have values from the form or not.

    BTW this is an AJAX grid and the update is occurring in the detail part.


    • #3
      Re: Force null on numeric SQL insert

      Do you actually have values of zero in your SQL tables? Or just null?
      If it is just null, which is my guess, then you could do this after the values are downloaded in alpha:

      You could run this script:
      t ="your_alpha_table")
      while .not.t.fetch_eof()
      if t.your_field=0
      t.your_field = NULL_VALUE()
      end if
      end while


      • #4
        Re: Force null on numeric SQL insert

        Thx. I'm not familiar with the code you mention as I'm new to Alpha. In the help file, table-open() looks like it works on the Alpha DB - whereas I have SQL Server.

        The best solution to me is for Alpha to only include in the INSERT statement the fields with values. I couldn't see a setting for that in the grid properties. It's including everything from the underlying query right now. Am I missing something or is this option just not there?


        • #5
          Re: Force null on numeric SQL insert

          Looks like this fix will address the issue:

          I will try it and confirm either way.