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



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

Update data dictionary on Network

  • Filter
  • Time
  • Show
Clear All
new posts

    Update data dictionary on Network


    When on a network, using network optimization, when referring to tables to update data dictionaries, does one reference the table through the local shadow database, or does one reference the actual data table (X:drive)on the network?

    Or does network optimization update dictionaries making an additional update unnecessary?



    RE: Update data dictionary on Network

    Hi Tom,

    Network optimization creates a new, or overwrites and existing, optimized database. This optimized database contains all the data dictionary files and a table file that 'points' to the real table file. A shadow_refresh copies the data dictionary files but does not update the shadow tables. If you don't change the table structure a refresh should be all you need. That said, I've had problems with the shadow refresh. Sometimes it appears to work but then gives an error when you try to open the shadow. It usually give an error message that would lead you to believe there is a path problem. Other times it just doesn't appear to work. I always do a complete network optimize whenever things need updated. Unfortunately, xbasic doesn't provide in version 4.5 the tools to properly automate this process. Sys_send_keys() can be used, but there are problems with this also. If I automate a network optimization in v4.5 from an existing shadow, it almost always works the first time, almost always doesn't work the second time. I think it has to do with alpha's name space arrangement. Good news is that v5 gives us the tools.



      RE: Update data dictionary on Network

      Hi Jim,

      Thanks for responding. What I find is that occasionally I need to update indexes manually when on one computer. If I put my application on a network, if I want to update indexes in a table, do I address it thru its shadow, or address the network drive, in this case X:?

      Or would I network optimize again to force tables to update indexes?



        RE: Update data dictionary on Network

        This will update your indexes but it does no error checking. No other users can be accessing the table when you update. Just put it on a button on your main form not on the open table.

        tbl ="Your_table_name")


          RE: Update data dictionary on Network

          Thanks Allen,

          I have a script that goes through all my tables and updates indexes, what I want to know is, when installed on a network, how does one reference the tables;

          e.g. tbl ="c:|A5V4|shadow|etc...) 'LOCAL DRIVE
          OR tble ="X:table reference) 'NETWORK DRIVE

          I'm guessing the latter, but...



            RE: Update data dictionary on Network

            Hi Tom,

            You'd reference your local shadow table just like normal, A5 takes care of the rest. You could address the table directly on the server, but I don't see a reason to do this in normal circumstances. Alpha will give you the path to the 'real' table via the 'a5.get_master_path()' function, but again just reference the table as you normally would. Indexes of course have to reside on the server as everyone on the network has to have the same indexes. Queries however reside locally.



              RE: Update data dictionary on Network

              If all of the tables are in the same folder you don't need the path at all only the table name server or workstation.


                RE: Update data dictionary on Network

                Thanks guys - you stay up later than I do!



                  RE: Update data dictionary on Network

                  Sorry guys, I don't totally agree with this.

                  First,a disclaimer: I'm not sure what "update_production_indexes" does because I seldom use it. I use an Xbasic script to completely rebuild the indexes because I want to make sure all extraneous indexes have been removed and, more important, all required indexes still exist. Unfortunately, I've run into situations where users delete indexes because they think they aren't necessary.

                  If you want to update the indexes, I recommend accessing the network file itself. I know that running the following script in a shadowed application will update indexes only on the local computer and not the network:

                  tp = "MyTable" )
                  table.index_create_begin( "LastName", "Last_name" )

                  To fix this you need:
                  tp = a5.get_master_path() +chr(92)+ "MyTable" )

                  If you want to find out what's happening on your system, try this:
                  1. Delete any .cdx files in your shadow directory - they shouldn't be there.
                  2. Run your index update.
                  3. Check your shadow directory again for .cdx files. If any are found, you didn't update the indexes on the network.


                    RE: Update data dictionary on Network


                    The table index file resides on the 'server'. When a shadow is created it does not bring in (copy over) the *.cdx to the shadow. The tables in the shadow are just a pointer to the real tables. This has to be, as there can only be one copy of the real data, just as there can be only one copy of the *.cdx file. Any index (not query) you use is the same one all users have access to.

                    In response to Cals' post I checked this out and he's right, .index_create_begin() does not work when run from a shadow without feeding it the master path. It will work if you point it to the server. I'm not so sure whether this is by design or if it's a 'feature'. Maybe it's a safety feature, but I doubt it. *.index_create_begin() creates a whole new production index, doing away with the old and replacing it with the new tags that you supply. *.index_tag_add() works as advertised, pointing it to the shadow table adds an index (tag) to the production index file on the server. *.update_production_index() also works by pointing it to the shadow.

                    The "update_production_indexes" command updates all the tags in the production index file (*.cdx), just as if you right clicked on the table icon and choose 'Update Indexes'.