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

Error on save

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

    Error on save

    I get this error when closing my DB:

    Script:OnSave line:50
    topparent.Commit()
    Argument is incorrect data type


    This is what I have as "OnSave"

    Code:
    'Date Created: 15-Aug-2005 03:26:18 PM
    'Last Updated: 16-Aug-2005 09:08:34 AM
    'Created By  : choens
    'Updated By  : Kevin
    'Date Created: 15-Aug-2005 08:44:21 AM
    'Last Updated: 15-Aug-2005 03:22:42 PM
    'Created By  : Kevin
    'Updated By  : choens
    t=table.get("trips")
    dim temptax as n
    topparent.Commit()
    If t.mstatus = "Married"
    select
       case t.trip_pay<=100
       		temptax=.162
       case t.trip_pay>100 .and. t.trip_pay<=205
       		temptax=.181
       case t.trip_pay>205 .and. t.trip_pay<=495
       		temptax=.201
       case t.trip_pay>495 .and. t.trip_pay<=600
       		temptax=.215
       case t.trip_pay>600 .and. t.trip_pay<=795
       		temptax=.219
       case t.trip_pay>795 .and. t.trip_pay<=900
       		temptax=.223
       case t.trip_pay>900
       		temptax=.225
    end select
    else
    select
       case t.trip_pay<=100
       		temptax=.192
       case t.trip_pay>100 .and. t.trip_pay<=205
       		temptax=.199
       case t.trip_pay>205 .and. t.trip_pay<=495
       		temptax=.207
       case t.trip_pay>495 .and. t.trip_pay<=600
       		temptax=.220
       case t.trip_pay>600 .and. t.trip_pay<=795
       		temptax=.225
       case t.trip_pay>795 .and. t.trip_pay<=900
       		temptax=.239
       case t.trip_pay>900
       		temptax=.250
    end select
    End if
    t.change_begin()
    	t.trip_tax=temptax
    t.change_end()
    topparent.Commit()
    topparent.Resynch()
    topparent.Refresh_Layout()
    Any idea? I don't see the error.. these fields are numeric.:(
    Kevin G. Timberlake
    Marvel Illusions

    #2
    The code immediately preceeding the second "topparent.Commit()" operates directly on the table and thus the "topparent.Commit()" at that point is unnecessary. I'm not sure exactly why that would throw an error.

    You will probably get the same error from

    topparent.Resynch() and
    topparent.Refresh_Layout()

    if you remove the commit line.

    I would try

    parentform.Resynch()
    parentform.Refresh_Layout()
    There can be only one.

    Comment


      #3
      Studying further I am puzzled by

      I get this error when closing my DB:
      and
      This is what I have as "OnSave"
      The code you indicate seems more appropriate to a form's cansave event.

      The form may be being closed as you "close the db" before the second topparent.commit() can execute, meaning there is no topparent to commit at that point.
      There can be only one.

      Comment


        #4
        Kevin,

        I agree with Stan, your code needs to be in the 'CanSave' event and does not need to have the topparent.Commit() since that is what is about to happen to trigger the 'CanSave'.

        I also don't think you need topparent.Resynch() and topparent.Refresh_Layout() since from what I see, your code is only effecting 1 field, "temptax". I would think that just refreshing the field itself would be quicker and easier(temptax.refresh()), but if the field effects others also, then leave them in.

        That brings me to my last observation, temptax. It should either be, t.temptax if its a field name, or temptax.value if its a form object. This might be whats throwing the error.

        Good luck,

        Scott

        Comment


          #5
          Thanks for the backup. I believe temptax is a variable from the

          dim temptax as n

          statement.

          On a completely different note I would suggest building the select case command structure like

          Code:
          select
             case between(t.trip_pay,0,100)
             		temptax=.162
             case between(t.trip_pay,100.01,205)
             		temptax=.181
             case between(t.trip_pay,205.01,495)
             		temptax=.201
             case between(t.trip_pay,495.01,600)
             		temptax=.215
             case between(t.trip_pay,600.01,795)
             		temptax=.219
             case between(t.trip_pay,795.01,900)
             		temptax=.223
             case t.trip_pay>900
             		temptax=.225
          end select
          Probably just a personal preference but it seems easier to read for me.
          There can be only one.

          Comment


            #6
            Well Duhhhhh ...

            Time to buy some glasses .. :D

            Forget what I said about temptax Kevin, I only had one cup of coffee :)

            Comment


              #7
              Thanks Guys,
              I am on the road, but will test this in a couple of days. I am uploading the form for you to look at better to see what I am doing. I am trying to make the "estimated tax" calculate from the "gross" and give a "net". The tax is variable by the gross amount.
              Kevin G. Timberlake
              Marvel Illusions

              Comment

              Working...
              X