Networking

[Charles Hoens]

First, thanks to Selwyn and the gang on fixing the network update problem. My program changes are now updating to all my users simply by changing the version number in the Network Optimize area.

However, here's another problem/request. Over the years I been using A5, I generally end up taking a copy of all the program files home with me via zip disk. At night, I then make the changes and reload it the next day onto the business server and then let everyone update from there.

The problem is that when I go home, I have to tell everyone NOT to make any updates or changes to the database, as those changes will be overwritten when I return the next day. Some days I skip a day before coming back to work, which means that they can't use the program, other than for lookups, until I get back.

Is there a method or strategy or better yet an enhancement to V6 whereby I could just update those screens or databases that I have changed? Generally, the work I am doing has nothing to do with the main dbf's, but with a new module I am adding, changing or fixing.

Any ideas or help would be greatly appreciated.

Charlie

[CALocklin]

RE: Networking

Charles, Charles, if you are not restructuring anything but only adding/modifying layouts and/or field rules, just copy the data dictionary files rather than the data files.

You can always copy the *.dd* (3 per table) and *.se* (3 per set) files back to the server without fear of affecting any data - as long as the field names, sizes, and positions haven't changed.

Here's the big question: If you are not storing any user info with A5.save_settings() and are either not using Alpha's built-in user/group security or are not worried that someone would have modified these settings, you can also copy the .al* files. All your global scripts and functions are stored in the .al* files. However, so are the security settings so copying those files will overwrite any changes to the security settings.

Another alternative is to keep all the global scripts and functions in a separate library (the 3 .al* files constitute a library) and just copy that to the server. This means that the Network Optimize would also have to include these files as additional files to be copied with the network optimize/refresh routine.

If you need to restructure, it gets more complex but it's actually pretty easy in your case. Since you will be right there to do it, just restructure the tables before you install your update. (It can also be restructured from the Autoexec routine but it's a lot more complicated.)

I do this kind of thing on a regular basis - including automating the restructure process through the autoexec. Once you've done a couple it's no big deal.

Cal Locklin
www.aimsdc.net

[Elke]

RE: Networking

I am currently using Remote Desktop Connection and it's not as difficult to set up as it seems.

http://www.microsoft.com/windowsxp/using/mobility/default.mspx

[CALocklin]

RE: Networking

Minor correction.

According to the Help file, library files in v6 that are linked to the application (from Control Panel - File / Database Properties / Libraries) will automatically be copied. No need to include them in the list of additional files to be copied during network optimization/refresh.

In v5 they must be added to the list of addition files to be copied.