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

.MPX file nightmare

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

    .MPX file nightmare

    I've read the threads about mpx files and seem to be confused.
    After updating to 1498 1051 I've noticed that the mpx are not going away. So first, I checked the shortcut start in path. It is set to C:\a5v5\rcl co\ and the directory setting is Windows temp. I started my app, click on a button which prompts for a record, selected a record and exited the program. Ran a search for mpx files and found two in the same path as the start in. Next I created a folder called a5mpx and set the directory private path to it. Deleted all mpx files. Restarted A5 selected a record as above and exited the program. Did another search and found 2 mpx files. One in the same path as shown in the start in (a5v5\rcl co and one in the folder a5mpx). I changed the start in to be the same as the private path, deleted the mpx files. Run the program again. This time I find 2 mpx files in the a5mpx folder. Not knowing what to do I went back to my orignal settings and reinstalled patch 1490 1047. No mpx saved anywhere. This is true for all builds prior to 1047. But begining with 1498 1050 the mpx files are saved to the path as shown in the start in.

    I this point (4 hours of tinkering) the results are the same and I am confused. As a last resort I reinstalled build 1490 1047 and have had no more mpx files saved. The end result for me is not to install any builds beyond this.

    Anyway my question is, has anyone else found a soultion other than deleting them manually? My opinion is this an Apha bug starting with build 1498 1050 since all earlier builds delete the mpx's when I exit.

    Hope this all makes since.


    #2
    RE: .MPX file nightmare

    Makes sense to me as I see the same behavior using XP pro. You didn't mention your operating system, did you?

    Bill
    Bill Hanigsberg

    Comment


      #3
      RE: .MPX file nightmare

      I'm also using xp pro at home with the same results and at work on the server using windows 2000. By the way I've tried every combination I could think of, changing start in paths, private path and so on. Same results beyond 1498 1047. What bummer for an old man like me.

      Comment


        #4
        RE: .MPX file nightmare

        here is a script by Cal Locklin
        open with startin in the normal fashion
        then use this in your close the database button

        'Date Created: 17-Nov-2002 08:45:54 AM
        'Last Updated: 17-Nov-2002 09:12:14 AM
        'Created By : Cal
        'Updated By : Cal
        '-----------------------------------------------------------------------
        ' THIS SCRIPT DELETES ALL FILES IN THE DATABASE THAT START WITH "$$".
        ' THIS INCLUDES THE DATA PATH (start-in), PRIVATE PATH, AND EXECUTABLES PATH.
        '-----------------------------------------------------------------------
        '@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
        '@ IT WILL NOT WORK WELL AS A *FUNCTION* IN THE AUTO-EXEC BECAUSE IT
        '@ TAKES TOO LONG TO FIRE FROM THERE. A FUNCTION WORKS FINE OUTSIDE
        '@ THE AUTO-EXEC SCRIPT.
        '@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
        '-----------------------------------------------------------------------
        ' SET THE PATH NAMES TO AN ARRAY FOR LOOPING.
        '-----------------------------------------------------------------------
        DIM path(10) as c

        path(1) = a5.get_path() + chr(92)
        path(2) = a5.get_private_path() + chr(92)
        pcount = 2
        IF a5.get_private_path() a5.get_exe_path()
        path(3) = a5.get_exe_path() + chr(92)
        pcount = 3
        END IF
        '--- DON'T BOTHER WITH THE SHARED PATH or MASTER PATH BECAUSE IT SHOULD
        '--- NEVER PUT THESE FILES THERE.

        '-----------------------------------------------------------------------
        ' NOW DELETE ANY "$$**.*" FILES THAT ARE NOT LOCKED.
        '-----------------------------------------------------------------------
        fcount = 0
        FOR x = 1 to pcount
        type_of_files = 0 + FILE_FIND_ARCHIVE + FILE_FIND_READONLY + FILE_FIND_HIDDEN
        dfiles = filefind.first( path(x) + "$$*.*", type_of_files )
        WHILE .not.dfiles.eof()
        fname = dfiles.name() '*** GET THE FILE NAME.
        ON ERROR goto Continue_next '*** FIND OUT IF THE FILE IS LOCKED.
        fp = file.open( fname, file_rw_exclusive )
        ON ERROR goto 0
        fp.close() '*** FILE IS NOT LOCKED SO CLOSE IT AND REMOVE IT.
        file.remove( fname )
        fcount = fcount + 1
        '---------------
        Continue_next:
        '---------------
        ON ERROR goto 0
        dfiles.next() '*** GET NEXT FILE IN LIST.
        statusbar.robot()
        END WHILE
        NEXT
        a5.close()
        Cole Custom Programming - Terrell, Texas
        972 524 8714
        [email protected]

        ____________________
        "A young man who is not liberal has no heart, but an old man who is not conservative has no mind." GB Shaw

        Comment


          #5
          RE: .MPX file nightmare

          Thanks Martin, guess this will have to do for now but still doesn't seem to the long term answer to this problem. I would have thought that Alpa would address this or at least mention that they reconize there is a problem and are looking into it.

          Comment


            #6
            RE: .MPX file nightmare

            William,

            I've never had problem with .mpx files other than the occasional one or two when looking at a db through explorer, however, after reading this thread today, returning back to A5 and then exiting A5 my desktop was covered with .mpx files, it was like a plague. Have the little bug!22#rs found a new way to attack us via the forum?. Do we need to go to color code alerts?

            It appears that I have now joined the exclusive .mpx club.

            Alan

            Comment


              #7
              RE: .MPX file nightmare

              William and Others,

              Getting the .mpx files on my desktop bugged me so I tried to follow the steps I took prior to accessing the forum, this I did successfully and and bingo 18 .mpx files on my desktop. These are my steps:

              1. went into form design, the existing form is based on a set with an embedded browse. minimized A5 and found 2 .mpx files on my desktop.

              2. max screen, went into the first field of the embedded browse, which is a date field, right click, select properties and click ok.

              3. minimize A5 and found another 16 .mpx files on the desktop. At this stage I have not exited from design mode.

              The form I went into has not been changed for months and this is the first time I have accessed it in design since the recent builds.

              I am using Xp pro.

              Hope this will help.

              Alan

              Comment


                #8
                RE: .MPX file nightmare

                Alan

                First, check out the other threads on the mpx file issue to verify your shortcuts to Alpha 5 and the database are correct. This is one of the big reasons for problems. However, there was a change in the way mpx files are handled in build 1494_1049. While this did fix one fairly serious problem with mpx files, it looks like the law of unintended consequences has struck. I also have seen mpx files in odd places.

                There do appear to be some patterns. If the problem is mpx files on the desktop, this is almost always a shortcut issue with a desktop icon with no path. You can force the mpx files to go to the private path in most cases by specifying a private path in A5 settings and then using the same path as the Start-in path on shortcuts. If the shortcut is in the private path, it will disappear - but only when a5 closes. Some mpx files will always be present when A5 is running since they hold query information. Any operation that uses a query such as a find, a form filter, queries themselves, and others, will build a mpx file.

                However, even if you do things right, sometimes mpx files are created in some other places. The problem is that these files seem to have little pattern, other than their locations. They end up in a database folder, the a5 program folder, or in some cases, the addins_installed subfolder under the A5 folder. I have seen a couple in the root directory, but these seem almost always to come from the shortcut issue. These odd mpx files are not always present, and as yet, there doesn't seem to be a defined set of conditions that cause them.

                Jerry

                Comment

                Working...
                X