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

C:\windows\temp\violated.mdx

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

    C:\windows\temp\violated.mdx

    The following post operation runs fine on the local webroot:

    a_tbl = table.open("[pathalias.adb_path]\patients")
    post.t_db = "[pathalias.adb_path]\appointments"
    post.m_key = "IDNUMBER"
    post.t_key = "IDNUMBER"
    post.m_filter = ""
    post.t_filter = "pracid='"+session.pracid+"'"
    post.m_count = 1
    post.m_field1 = "Totalptbal"
    post.m_exp1 = "if(respname<>\"\",Totalptbal+@Appointments->Ptbal,Totalptbal)"
    post.t_count = 0

    a_tbl.post()
    a_tbl.close()

    However, when run on the remote server, I get the following error:

    500 Internal Server Error
    "Script Error
    Error:Script: /amav5.0/Print_Insurance_Paper_Pt_Unbilled_Bill.a5w line:104
    a_tbl.post()
    The system cannot find the file specified.
    C:\WINDOWS\TEMP\VIOLATED.MDX"

    Does anyone have a clue as to what this means?

    Gary
    Gary S. Traub, Ph.D.


    #2
    Re: C:\windows\temp\violated.mdx

    Someone I know had the same issue with a posting problem. When he replaced the [pathalias.adb_path] with the actual path [c:\a5_data] It worked. See if that will do it for you.
    Dan

    Dan Blank builds Databases
    Skype: danblank

    Comment


      #3
      Re: C:\windows\temp\violated.mdx

      Dan,

      Indeed that worked!

      Thanks - it really is much faster to use an operation than xbasic.

      Gary
      Gary S. Traub, Ph.D.

      Comment


        #4
        Re: C:\windows\temp\violated.mdx

        I am experiencing a similar problem.

        This does not work-
        File.Append_Line("PathAlias.ADB_Path]\EmailLog.txt",Empname+" email sent on "+vTime+" was successful "+ipaddress)

        This does work-
        File.Append_Line("d:\data\mbcsupport\logs\EmailLog.txt",Empname+" email sent on "+vTime+" was successful "+ipaddress)

        However, everywhere else I use the alias it works find. Such as-
        filename = report.saveas("Ticket@[PathAlias.ADB_Path]\tickets.dbf","PDF",filter,order,filename,.f.)

        Is this a bug? For portability, I cannot use a hard coded path.
        Tommy Thompson
        Thompson Consulting Services
        Beautiful Kentucky Lake, Springville, TN 38256
        [email protected]

        Comment


          #5
          Re: C:\windows\temp\violated.mdx

          Hi Tommy,

          Well after reading this thread, I am thinking it must be a bug. I was curious to see if that would work for Gary, and it has. So, now there are three cases where the pathalias.asb doesn't work for a post operation.

          Since you have an example of this, go ahead and report it as a bug.
          Dan

          Dan Blank builds Databases
          Skype: danblank

          Comment


            #6
            Bug response from Selwyn

            it sounds like aliases are not getting resolved by the file.append_line() method.


            you can easily work around this by doing this:

            dim fn as c
            fn = filename_decode("[PathAlias.ADB_Path]\logs\EmailLog.txt")
            File.Append_Line(fn,Empname+" email sent o
            Tommy Thompson
            Thompson Consulting Services
            Beautiful Kentucky Lake, Springville, TN 38256
            [email protected]

            Comment


              #7
              Re: C:\windows\temp\violated.mdx

              Tommy,
              Thanks for the work-around....in case it is not fixed. Did you submit your example to Alpha as a Bug report? If so did you receive word back?
              Last edited by MikeC; 05-16-2009, 03:00 PM. Reason: i before e, except....
              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


                #8
                Re: C:\windows\temp\violated.mdx

                Originally posted by Tommy Thompson View Post
                This does not work-
                File.Append_Line("PathAlias.ADB_Path]\EmailLog.txt",Empname+" email sent on "+vTime+" was successful "+ipaddress)

                This does work-
                File.Append_Line("d:\data\mbcsupport\logs\EmailLog.txt",Empname+" email sent on "+vTime+" was successful "+ipaddress)
                Does this work?
                File.Append_Line("[PathAlias.ADB_Path]\EmailLog.txt",Empname+" email sent on "+vTime+" was successful "+ipaddress)
                Al Buchholz
                Bookwood Systems, LTD
                Weekly QReportBuilder Webinars Thursday 1 pm CST

                Occam's Razor - KISS
                Normalize till it hurts - De-normalize till it works.
                Advice offered and questions asked in the spirit of learning how to fish is better than someone giving you a fish.
                When we triage a problem it is much easier to read sample systems than to read a mind.
                "Make it as simple as possible, but not simpler."
                Albert Einstein

                http://www.iadn.com/images/media/iadn_member.png

                Comment


                  #9
                  Re: C:\windows\temp\violated.mdx

                  Before we call it a bug, Gary can you upload the code and tables required to reproduce this.
                  Steve Wood
                  See my profile on IADN

                  Comment


                    #10
                    Re: C:\windows\temp\violated.mdx

                    Hi Steve, Just write a post operation then publish it to a server and see if it will work for you. (Remember it works on the local host) I have two clients that the posting operation would not work with ("[pathalias.adb_path]\table_name") . Plus I recently tested it on my site and found it would not work. Then that also seems to be the case with Gary.

                    If it works for you let us know. I am interested in the results.

                    That is for the posting operation. I have not tried the File.Append_Line. No comment on that.
                    Dan

                    Dan Blank builds Databases
                    Skype: danblank

                    Comment


                      #11
                      Re: C:\windows\temp\violated.mdx

                      Well, this works for me:

                      Code:
                      <%a5
                      a_tbl = table.open("[pathalias.adb_path]\post_master")
                      post.t_db = "[pathalias.adb_path]\post_tran"
                      ?"Trans: "+ post.t_db
                      post.m_key = "ID"
                      post.t_key = "ID"
                      post.m_filter = ""
                      post.t_filter = ""
                      post.m_count = 1
                      post.m_field1 = "Post_Master"
                      post.m_exp1 = "@Post_Tran->Post_Value"
                      post.t_count = 0
                      a_tbl.post()
                      a_tbl.close()
                      
                      file.append_line("[pathalias.adb_path]\mytest.txt",post.t_db)
                      %>
                      tests both the file.append_line() and post transaction.

                      Gary - you have a really long filename "Print_Insurance_Paper_Pt_Unbilled_Bill.a5w" and also a period in the path text, and the error says it cannot find the page, nothing to do with the post operation. What is the entire script?
                      Steve Wood
                      See my profile on IADN

                      Comment


                        #12
                        Re: C:\windows\temp\violated.mdx

                        Interesting?? Steve are you running this on a web page or from a dialog component? I guess same question for Gary and Tommy. I know my errors are coming from a dialog component.
                        Dan

                        Dan Blank builds Databases
                        Skype: danblank

                        Comment


                          #13
                          Re: C:\windows\temp\violated.mdx

                          Hi Dan,

                          I am running this from an a5w page.

                          Hi Steve,

                          That really long file name does not cause me problems anywhere else other than the post operation. Also, looking at some of alpha's own examples, they also use really long file names. Finally, hard coding the path works so doesn't that rule out the filename length as the real issue here - sounds more like a problem in resolving the alias (as mentioned above) (perhaps just for long file names), doesn't it? Which perhaps is only an issue with the post (or append) operation?

                          Gary
                          Gary S. Traub, Ph.D.

                          Comment


                            #14
                            Re: C:\windows\temp\violated.mdx

                            That's why I wanted your whole script and associated tables, to test properly. It's easy to determine what the alias is at runtime. There are several functions that have peculiarities, for instance the record_add() function (and the other functions in that family) mandates ".dbf" in the expression, whereas other functions assume the extension.

                            "Functions" don't resolve an alias, the alias is supposed to be resolved at runtime, or publish time, depending on your setting. It's just a variable. I could test your code to see what the alias and full path is at the time the code fires.

                            You also have a more complex expression for your post, compared to my simplistic example, so that could be part of the issue. Maybe your code works perfect on my server, and not on yours, which will help clarify the issue. Selwyn is going to need more information if it is turned in as a bug.
                            Steve Wood
                            See my profile on IADN

                            Comment

                            Working...
                            X