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

Alternate form appearance for database copies?

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

    Alternate form appearance for database copies?

    We have a pretty common practice of copying our database for various reasons: training copies, development copies, backups, etc. I have an Autoexec script that can detect an alternate database, and I would like to change the form appearances to make the change immediately obvious to the user. My preferred method would be changing our standard teal background to, say, orange.

    What are some possible ways of making this change? Are stylesheets the way to go? (I'm not familiar with their use inside Alpha Five.) Is is possible to iterate through the forms using a5.form_enum() and modify the background color during Autoexec? Possibly some other way I'm not familiar with?

    Thanks for any help you can provide.
    Adam Backstrom <[email protected]>

    #2
    Re: Alternate form appearance for database copies?

    For one client I put a conditional object at the top of each form, with one condition displaying Practice. The autoexec was hard coded to set a global variable depending on the drive & directory of the database, and used to make the choice in the conditional object.
    -Steve
    sigpic

    Comment


      #3
      Re: Alternate form appearance for database copies?

      I'm loathe to do it per-form, since we're up to 128 forms at the moment. :) It would have to be something added to each form programatically, like a modification of the <form>.OnInit method.
      Adam Backstrom <[email protected]>

      Comment


        #4
        Re: Alternate form appearance for database copies?

        Adam

        Note that the form.load() method allows you to designate a stylesheet.

        So in combination with Steve's idea, you could change the stylesheet to change some colors also.
        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


          #5
          Re: Alternate form appearance for database copies?

          The database I referred to has over 200 forms, but lots of menus and submenus. So we didn't change 'em all -- just those key parts. You might consider whether you really need to do this with all forms.

          I like Al's suggestion of selecting the stylesheet.

          Another thing you can do is adjust the a5.window_title. Use lots of asterisks, etc. to help draw attention to the difference when needed.

          One more thought: I'll bet the majority of your forms use the same two or three toolbars or custom menus. You could make use of them quite easily.
          Last edited by Steve Workings; 08-29-2006, 05:55 PM.
          -Steve
          sigpic

          Comment


            #6
            Re: Alternate form appearance for database copies?

            Hi Adam,
            I use several shortcuts with the -include= statement to load Alpha with a text file for each of my copies that changes the A5 title bar. I also have a conditional object on my Main Menu form that displays a button when it is the Server copy - setting a global variable in the Autoexec. This could easily display text instead. Another advantage of the window title is that the taskbar will show it when the program is minimized in case two or more copies are open. You can also add different splash screens or icons in the text file that would give a visual reminder.
            Robin

            Discernment is not needed in things that differ, but in those things that appear to be the same. - Miles Sanford

            Comment


              #7
              Re: Alternate form appearance for database copies?

              I created a small example that I thought may be relevant to this discussion but it doesn't fully work. I wonder if someone would have a minute or two to confirm the nonworking status. If confirmed and I haven't made a glaring mistake I will submit a Bug Report. What the sample does is use the database custom colors. Once a custom color is defined it is then available where ever a color needs to be chosen. If this custom color is used throughout the application and the definition is changed then the change is reflected throughout. Pretty handy I thought. There are also a couple of functions that can be used to redefine this color with xBasic. I figured code in the autoexec could check for a condition and set this custom color. In my sample the code I have actually does alter the definition but the color does not change unless the Settings dialog is opened to the color paramater Option and then closed with the Ok button. To see this do the following:

              --Open Form1
              --press the 'change color' Button 'the value that appears should be the current green value.
              --enter a new value and press OK 'tip--change the value by a lot so the color change is obvious
              --close the form
              --open the form 'the color hasn't changed
              --go to the main Alpha menu->view->settings->expand the Database branch and choose color. ' you will see that the green value is changed to the value you entered and the color in the dialog is the new color.
              --Click OK to close the settings dialog 'without doing anything else in the dialog.
              --adjust the size of the form so that it repaints and voila the color updates.

              If the Settings dialog is closed with the cancel button the color does not update in the app even though the definition has changed.
              It is as if the info is not getting written into a definition file somewhere.

              TIA for any assistance
              Last edited by Tim Kiebert; 09-02-2006, 11:33 AM.
              Tim Kiebert
              Eagle Creek Citrus
              A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

              Comment


                #8
                Re: Alternate form appearance for database copies?

                Originally posted by abackstrom
                I'm loathe to do it per-form, since we're up to 128 forms at the moment. :) It would have to be something added to each form programatically, like a modification of the <form>.OnInit method.
                Have your autoexec code dim a global character variable to a color name. Then put the following in the OnInit of your forms
                Code:
                Dim Global theglobalvariable as C
                topparent.Fill.Forecolor  = theglobalvariable
                Tim Kiebert
                Eagle Creek Citrus
                A complex system that does not work is invariably found to have evolved from a simpler system that worked just fine.

                Comment

                Working...
                X