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
Devcon 2020 Goes Virtual! LEARN MORE >

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

Updating AutoExec Variables

Collapse
X
Collapse
 
  • Page of 2
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 template Next
    #16
    Re: Updating AutoExec Variables

    Originally posted by jbk View Post
    I tried your updated code you posted/modified in thread #8 about 35 minutes ago. Have you posted code since then?
    Post # 8

    Comment

      #17
      Re: Updating AutoExec Variables

      I want the code to produce the file path C:\Users\Steve\Desktop\Steve Martin Sales Data thru "SCLDATE".zip Where SCLDate is determined by the "Date" of the last sales call in the table "Sales Data" in the example. I think if you input a couple example sales calls with todays date (4/13/12) you see what I mean. Just modify the file path to match you output (ie C:\Users\Gabriel\Desktop\G Gabriel Sales Data thru" ) Thanks for everything....

      GO SAINTS!!!!

      Comment

        #18
        Re: Updating AutoExec Variables

        Originally posted by jbk View Post
        I want the code to produce the file path C:\Users\Steve\Desktop\Steve Martin Sales Data thru "SCLDATE".zip Where SCLDate is determined by the "Date" of the last sales call in the table
        That's why I was wondering earlier why do you want that date in the xdlg?
        I have a very busy weekend..but this should be a very simple matter. I will get to it soon.
        I am assuming everything else is working as you wanted?

        Comment

          #19
          Re: Updating AutoExec Variables

          Basically the reason for the Xdialog is so that I can update the variable values. When I hire new employees and distribute our program to them, I have to open the autoexec script and make changes. With the Xdialog, I will be able to hit a button and make necessary changes. For the file path "C:\Users\Steve\Desktop\Steve Martin Sales Data thru "SCLDATE".zip " the only part of this I would update would be the salesman's name. For example: "C:\Users\Steve\Desktop\Steve Martin Sales Data" would be modified in the autoexec script to "C:\Users\Bob\Desktop\Bob Jones Sales Data" assuming I hired a salesman named "Bob Jones". I have several file paths some for zip files, others for importing and exporting data that would need similar modifications to the "file path". It would be nice to be able open a Xdialog and make changes.

          Thanks for everything...

          Comment

            #20
            Re: Updating AutoExec Variables

            Jon:
            That wasn't my question. I got that part that you want to pop up an xdlg and update the data.
            The part I don't get is: why do you want the SCLDate to show in the xdlg (which means the user, i.e. you, could change that date) but yet in your script you want it to gather the most recent date?
            Which one do you want? Set it yourself from the xdlg? or use an expression to get the most recent date?

            That said, it brings up another issue:
            In your table, you have the salesID as autoincrement. So, if you enter Steve martin more than once, it will have multiple sales ID's !
            I will be back later this evening. Hopefully by then we will have a more clear picture.

            Comment

              #21
              Re: Updating AutoExec Variables

              Thanks again for the response. The only part of the SMData variable that I want to have the "option" to change is the file path ie "C:\Users\Steve\Desktop\Steve Martin" I would still like the script to gather the most recent date. When I would modify the SMData in the original AutoExec script, I would simply open the Autoexec script thru the control panel and change the file path. Because the file path is now embedded in the script's code, doesn't seem possible to modify as needed. Is there a way of keeping this variable(SMData) out of your script and have it in the Autoexec's script. I have tried to take out the SMData line of code in your script and place the original SMData code back in Autoexec but everytime I hit "update" , it erases SMData code. Extremely important that I have this variable working like in my original post. Thanks again....

              Comment

                #22
                Re: Updating AutoExec Variables

                Gabriel, attached is an example of what myself and you have been working. I did some modifications but couldn't figure out how to make the variable SMData update the sales date using SCLDate and allow ME to modify the file path. In the example, you will see that the last sales call date (SCLDate) appears in the Xdialog box, but this is simply there to see that when the user changes the date of the sales call, it updates in the Xdialog box. The way I made it immediately update the date is by putting "script_play("autoexec") in the on press of the save button. I noticed that the date in the SMData only updates if you hit "update" in the Xdialog box. For example, if you open the sales data form, and change the data to i.e 5/01/12, then open the Xdialog box you'll notice that the SCLDate is now "5/01/12" but the date in the SMData field is the previous "last sales call date" until you hit "Update" and reopen Xdialog box. Is there any way of placing code or a script that when the user presses "save" it will automatically update Xdialog box, similar to the script_play(autoexec) does for SCLDate. If not, is it possible to place the SMData back into the Autoexec script. And if I need to modify the file path, I will simply open the script in design mode and make changes. Right know, if I place the any variables into autoexec script, they are instantly deleted when update button in the Autoexec Update script is pressed. It would be nice if the Update button did exactly that updated or amend variables but didn't replace or delete others.

                thanks again...JON
                Attached Files

                Comment

                Previous 1 2 template Next
                Working...
                X