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

a5.4.5 bug?

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

    a5.4.5 bug?

    I ordered 4.5 upgrade a few days ago I had a problem getting the download to work. At 10 PM I sent an email to customer service. At 8 Am the next morning I had email replies from the webmaster and another person at alpha. The problem had been fixed. When I got home from work there was a call on the machine from Richard Rabins. I should have called him back and told him everything was ok but I didn't get it done.

    This is great Service!!

    Now for the problem. I installed 4.5 and a script that has been running for fine for over a year now generates an error code.

    Debug(1)
    fv=a_field_value
    dr=Deposit_line->donor_id
    cn=lookupc("L",dr,"deposit->Check_number","deposit_line.dbf","donororder")
    IF .NOT.(val(cn)+50>val(fv) .and. val(cn)-10

    #2
    RE: a5.4.5 bug?

    I just remembered I need to tell you that Deposit_line is the table that is open when script needs to run.
    Thanks
    Ken Cameron

    Comment


      #3
      RE: a5.4.5 bug?

      I just remembered I need to tell you that Deposit_line is the table that is open when script needs to run.
      Thanks
      Ken Cameron

      Comment


        #4
        RE: a5.4.5 bug?

        I think your lookup should be:
        lookupc("L",dr,"Check_number","deposit_line.dbf","donororder")
        because the "Check_number" should be a field in the "deposit_line.dbf".

        If this doesn't solve the problem, could you confirm (a) where this script is (it looks like a CanWriteField event), and (c) is
        C:\program\a5v4\bethany\deposit_line.dbf
        the correct file name?

        In particular, the program part looks suspicious. More common would be Program Files.

        Comment


          #5
          RE: a5.4.5 bug?

          Thanks Cal I'll try that.
          I think the program part is ok- the Alpha must be to find the file, it has the file open and records can be entered and saved. Some small bit of syntax must be different in 4.5.

          Thanks
          Ken

          Comment


            #6
            RE: a5.4.5 bug?

            I just tried your sugestion It didn't work

            Thanks for trying
            Ken

            Comment


              #7
              RE: a5.4.5 bug?

              Any chance you can post your database (or at lease enough of it to illustrate the problem) ?

              Comment


                #8
                RE: a5.4.5 bug?

                Hi
                Here is the Database
                Go to the deposit entry form

                try to add a record to the Browse put in a check number a script will run, it will say can't find file The file it is trying to find is the browse. This script worked under a5.01-.04 will not work under a5.4.5
                Any help will be appreciated.

                Ken Cameron

                Comment


                  #9
                  RE: a5.4.5 bug?

                  Hi
                  Here is the Database
                  Go to the deposit entry form

                  try to change a check number a script will run, it will say can't find file The file it is trying to find is the browse. This script worked under a5.01-.04 will not work under a5.4.5
                  Any help will be appreciated.

                  Ken Cameron

                  Comment


                    #10
                    RE: a5.4.5 bug?

                    Hi
                    I fouled up, the files I sent will not work. Please disreguard the two preceeding posts. I'll try again.

                    Here is the Database
                    Go to the deposit entry form

                    try to add a record to the Browse put in a check number a script will run, it will say can't find file The file it is trying to find is the browse. This script worked under a5.01-.04 will not work under a5.4.5
                    Any help will be appreciated.

                    Ken Cameron

                    Comment


                      #11
                      RE: a5.4.5 bug?

                      Here's your check number global script:

                      Debug(1)
                      fv=a_field_value
                      dr=Deposit_line->donor_id
                      cn=lookupc("L",dr,"check_number","Deposit_line.dbf","donororder")
                      IF .NOT.(val(cn)+50>val(fv) .and. val(cn)-10

                      Comment


                        #12
                        RE: a5.4.5 bug?

                        Ken, please ignore the previous post. I did not understand the parameters you were using with lookupc(), so my suggestion is mistaken. Will keep digging.

                        A suggestion: Try using lookupc() on an external table that is not already open. This will verify whether lookupc() was broken when vers. 4.5 was released. If it works with a table that is not already open, consider the fact that in your case the deposit_item table *is* already open when your script runs. Perhaps you need to open another instance of the table to search for the contributor's last check.

                        -- tom

                        Comment


                          #13
                          RE: a5.4.5 bug?

                          Ken, I've been able to replicate the problem here. Your script works fie under vers. 4.03, build 230, but not under vers. 4.5

                          Comment


                            #14
                            RE: a5.4.5 bug?

                            Thanks Tom

                            Would a work around be setting up a table with donor_ID and check_number and with a post to replace check number each time a record is added.

                            Ken

                            Comment


                              #15
                              RE: a5.4.5 bug?

                              I just picked up on this thread. I am also having a problem
                              with lookupc in ver 4.5

                              Mine looks up the customer number from AR for an invoice number input.

                              In my case, it works some of the time only. The user picked up on the fact that it works only if the transaction date
                              was after 01/01/2001. I know this has nothing to do with
                              the lookup per se, but there does seem to be a relationship.
                              I can't make it work, and it's driving me insane.

                              Lowell

                              Comment

                              Working...
                              X