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

How to change field rules on a clients machine?

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

    How to change field rules on a clients machine?

    I have a client that is many miles away using the runtime. They have to have a field rule changed in order to turn off auto-incrementing. What is the fastest way for me to achive this task?

    Thanks in advance,
    Noble D. Bell

    #2
    RE: How to change field rules on a clients machine

    Make the changes, and send the .ddx, .ddm and .ddd file. That should do the trick. I have had to do this a few time for our plant in TN.

    Mick

    Comment


      #3
      RE: How to change field rules on a clients machine

      I guess this will not harm the clients data in any way??

      Comment


        #4
        RE: How to change field rules on a clients machine

        NO, it doesn't in any way harm the client's data, and as a plus, it keeps you in control. If all of the changes occur on your machine, you at least know what their machine should look like when they call with a problem. I have 5 clients around the county all running the same system, If each had a different dictionary, I wouldn't know how I would be able to maintain them. Now, all I need to do is make the fix and then create an install disk for them which copies the appropriate files to their machines. I use "Install Shield" It works great.

        Comment


          #5
          RE: How to change field rules on a clients machine

          Follow on from previous questions.

          Once a runtime application is running on the clients computer and with no access to the contol panel, the .dbf, .cdx, .fpt files change with data entry.

          Do any other files change in normal runtime use? For example, do any of the set files change?

          Where do the calculated field rules get stored? I would expect these to change with data entry.

          Appreciate any comments

          Michael

          Comment


            #6
            RE: How to change field rules on a clients machine

            The Dictionary files of a table are where the field rules, field definitions, forms,reports, letters, etc. are stored. When you make changes to forms, field rules, etc, you are only affecting the dictionary files. (.DDD, .DDM, .DDX). If you were to make changes to the structure of the table, ie add a field, or modify the length of the field, then you would need to do something like copy out to the new format and remove the old table. I just yesterday found a problem with an append in one of my tables. I made the change, copied the three files (DDD, DDM, DDX) to diskette, then mailed the changes (with an install routine) out to my clients. They are very used to doing this kind of fix. They don't need to know how things got fixed, just that after running the change, everything is ok.

            A Set is just a dictionary of logically linked tables. Indexes and DBF structures are taken from the individual tables. If you look at a set, the index used is from the parent table in the set. If changes are made to forms, etc in the set, just copy the SEM, SET, and SEX files, and they will be reflected on your client's machine.

            Comment


              #7
              RE: How to change field rules on a clients machine

              Hi again Thomas,

              My doubts are with a calculated field set up in field rules.

              Suppose your client has a calculated field name Mycalc and it gets its value from FieldA*FieldB. As I understand it, Mycalc value is stored in .ddd until a change is made in either FieldA or FieldB. What happens if you overwrite the clients data loaded .ddd files with the originals before any data had been entered. Is Mycalc now zero?
              With the full version the client could re-evaluate the field rules but not possible with Runtime.

              I also send the client a new update operation that updates either FieldA or FieldB like FieldA*1. I am never certain that my method is necessary.

              Peter Wayne's book say that the 'Field rules are saved with the .dbf where they belong' but I have not found this to be true.

              I would dearly like to get this clear in my own mind.

              Michael

              Comment


                #8
                RE: How to change field rules on a clients machine

                Michael,

                The field rules are stored in the Data Dictionary files for the table (*.ddd,*.ddm,*.ddx). Field Rules are only active while you are in enter or changing of a record. When you save the record, and values of calculated fields (of the field rules, not the forms' calculated fields) are stored in the field. The expression itself and data dictionary are still unchanged.

                Does that make sense to you now?

                Regards,

                Ira J. Perlow
                Computer Systems Design & Associates
                [email protected]
                Regards,

                Ira J. Perlow
                Computer Systems Design


                CSDA A5 Products
                New - Free CSDA DiagInfo - v1.39, 30 Apr 2013
                CSDA Barcode Functions

                CSDA Code Utility
                CSDA Screen Capture


                Comment


                  #9
                  RE: How to change field rules on a clients machine

                  Ira,

                  Thanks, got it quite clear now. The value of the field rule calculated field is still in the clients .dbf. Obvious now and Thomas's routine is adequate.

                  My updates have not been necessary.

                  Thanks again

                  Michael

                  Comment

                  Working...
                  X