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

Variable Type "H"

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

  • Variable Type "H"

    I have tried to use the action script to create a new record using xbasic to add a record which contains a html memo field.

    A5 dimmed the variable type for the html field as "H" which i am assuming means html. Regardless, when the script is run alpha does not recognize "H" as a valid variable type.

    Since A5 dimmed the variable itself should it not then recognize it?

  • #2
    Re: Variable Type "H"

    I've had a look through help and can't see a variable data type "H"

    Comment


    • #3
      Re: Variable Type "H"

      David,
      I couldnt find it either. However, A5 still dimmed it as "H" in my action script

      Comment


      • #4
        Re: Variable Type "H"

        I added a button to form, which executed a script via xbasic. The script added a new record, setting an HTML Memo field to the value "Test". The script ran fine.

        I converted the script to in-line xbasic... here's the code... is this what you're referring to? It's not dimming the field as "H".

        'Open the table that you want to update...
        dim tbl as p
        tbl = table.open("tblclaims",FILE_RW_SHARED)

        tbl.enter_begin()
        tbl.HTMLTEST = "Test"
        tbl.enter_end(.t.)
        tbl.close()

        Comment


        • #5
          Re: Variable Type "H"

          Tony,
          Could just be an anomaly, quirk, whathaveyou.....earlier today I noticed after messing with a couple of calculated definitions, they showed up in the xy dialog box's bottom left side of the status bar as a type Z (zee). And I know this is not a variable type. Once I got the calculation to work as I wanted and leaving Alpha and coming back, it shows as N as it should.
          Mike
          __________________________________________
          It is only when we forget all our learning that we begin to know.
          It's not what you look at that matters, it's what you see.
          Henry David Thoreau
          __________________________________________



          Comment


          • #6
            Re: Variable Type "H"

            Hi Tony,

            I can't speak to the cause of an action script DIM'ing as H (It would be useful if you could show the action or post some code here), however, I have compiled a list of various types that help highlight some of this. I suspect there is a minor bug with the action script. Type "H" was added to the Memo field types in A5v9.

            The types are basically defined as

            ' Types actually stored in a DBF Table Structure
            ' C=Character
            ' N=numeric
            ' L=Logical (width 1)
            ' D=Date (width 8)
            ' T=Time (width 17)
            ' Y=Short Time (width 9)
            ' E=ExponentNumeric (width 20)
            ' K=UUID (width 32) A5v9
            ' M=Memo (width 10)
            ' M=Bitmap Memo (width 10)
            ' M=OLE Memo (width 10)
            ' M=Rich Text Field Memo (width 10)
            ' M=JPEG image Memo (width 10)
            ' M=Image File Reference Memo (width 10)
            ' M=HTML Memo (width 10) A5v9

            ' Variable types allowed in XBasic Code
            ' A=Any Type
            ' B=Blob
            ' C=Character
            ' D=Date
            ' F=Function
            ' L=Logical
            ' N=numeric
            ' P=Pointer
            ' T=Time
            ' U=Collection
            ' Y=Short Time
            ' Z=Undefined (Null) Type
            ' K=UUID (A5v9)
            ' I=I Type (This type is unknown in it's usage)

            ' non-Memo field types (Data types as stored in the Data Dictionaries)
            ' C=Character
            ' N=numeric
            ' L=Logical (width 1)
            ' D=Date (width 8)
            ' T=Time (width 17)
            ' Y=Short Time (width 9)
            ' E=ExponentNumeric (width 20)
            ' K=UUID (width 32) A5v9
            ' Memo field types (Data types as stored in the Data Dictionaries)
            ' M=Memo (width 10)
            ' B=Bitmap image Memo (width 10)
            ' O=OLE Memo (width 10)
            ' R=Rich Text Field Memo (width 10)
            ' J=JPEG image Memo (width 10)
            ' I=Image File Reference Memo (width 10) (Not sure if L and I are the same or different)
            ' L=Image File Reference Memo (width 10) (sometimes referred to as a LINK field)
            ' H=HTML Memo (width 10) A5v9

            Main questionable areas are Type I in the variables and Type I/L in the Dictionaries.

            I hope this helps some!
            Last edited by csda1; 07-20-2008, 09:19 AM.
            Regards,

            Ira J. Perlow
            Computer Systems Design


            CSDA A5 Products
            New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
            CSDA Barcode Functions

            CSDA Code Utility
            CSDA Screen Capture


            Comment


            • #7
              Re: Variable Type "H"

              Thanks guys. A lot of good info. For what it is worth, I have been able to consistantly reproduce the problem.

              Here is the xbasic for the action script. Note the variable type H.

              Code:
              'Open the table that you want to update...
              dim tbl as p 
              tbl = table.open("test",FILE_RW_SHARED)
              'Use an Xdialog box to prompt for field values.....
              dim flag_ok_selected as l
              flag_ok_selected = .f.
              '
              DIM  Prompt_var_1 as H
              DIM  ui_get_parameters_result as C
              Prompt_var_1 = convert_type("","H")
              ok_button_label = "&OK"
              cancel_button_label = "&Cancel"
              ui_get_parameters_result = ui_dlg_box("Enter field values",<<%dlg%
              {region}
              Htmlfield:| [.40Prompt_var_1];
              {endregion};
              {line=1,0};
              {region}
              <*15=ok_button_label!OK> <15=cancel_button_label!CANCEL>
              {endregion};
              %dlg%,<<%code%
              if a_dlg_button = "ok" then 
              	flag_ok_selected = .t. 
              end if 
              
              %code%)
              if ui_get_parameters_result <> "OK" then 
              	end 
              end if 
              	
              tbl.enter_begin()
              tbl.HTMLFIELD = prompt_var_1
              tbl.enter_end(.t.)
              tbl.close()
              Also note that this action script produces an error and wont run.
              T

              Comment


              • #8
                Re: Variable Type &quot;H&quot;

                Hi Tony,

                Originally posted by reynolditpi View Post
                .... Note the variable type H.

                Code:
                ....
                DIM  Prompt_var_1 as H
                DIM  ui_get_parameters_result as C
                Prompt_var_1 = convert_type("","H")
                ....
                If you change the XBasic code line
                DIM Prompt_var_1 as H
                to
                DIM Prompt_var_1 as C
                it should work. "Type "H" in a memo field is treated as type "C" in XBasic.

                However, whatever action script you were doing, has a bug in it that generates it as type "H", which is wrong. Since people using Action Scripts don't necessarily understand the code that it is generating, it is easier for a bug like this to slip into the code, particularly with new data types, as they don't look at the underlying code and can only recognize a bug when it causes a noticeable error.


                Let us know what action script line you are using and it's parameters that generates the offending code, and report the bug to Alpha.
                Regards,

                Ira J. Perlow
                Computer Systems Design


                CSDA A5 Products
                New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                CSDA Barcode Functions

                CSDA Code Utility
                CSDA Screen Capture


                Comment

                Working...
                X