Hans-Christian Andersen
hans.andersen at phulse.com
Tue Mar 5 00:08:06 CST 2013
Hi Jim, Try looking at everything else outside the contents of the CMD.EXE windows. This is what I'm referring to. - Hans * * On 4 March 2013 20:14, Jim Lawrence <accessd at shaw.ca> wrote: > I wasn't going to comment but those are just menus assembled using > power-scripts. Every server-system guy use to build these to speed up their > production...hardly a GUI more like a simple batch file printing ASCII > characters to the screen and written in something like Term, EDI, GEdit or > VI. > > Here are some simple samples of how to create menus using advanced-enhanced > Bash type scripts: > > https://code.google.com/p/bashsimplecurses/ > > Many years ago, I built a series of menus for the PDP11-70 VMS to manage > tape backups, version control, monitoring volume resources and printing to > the plotter. Followed that up with building menus so clients could access > all their application on their PC, built menus so managing a Novell and > SCO-UNIX networks were faster. If you wanted to get fancy you could also > assembled them with such power tools as X-Windows, Perl scripts or even use > the old Lynx command line browser. These were hardly GUIs...just using the > good old common sense rule to always automate and use what ever tools are > available. > > I hope using these tools did not disqualify me from ever being a expert > system-network-server administrator and just relocated me to being little > more than a script-kiddie? ;-) > > Jim > > -----Original Message----- > From: accessd-bounces at databaseadvisors.com > [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Benson > (VBACreations.Com) > Sent: Monday, March 04, 2013 6:38 PM > To: 'Access Developers discussion and problem solving' > Subject: Re: [AccessD] New Approach > > Call that GUI ha ha ha. >