Results 1 to 5 of 5
  1. #1
    Join Date
    Nov 2005
    Posts
    2

    DBASE III Plus: DOS command line syntax???

    I am trying to totaly automate a simple database manipulation. If I invoke dbase then enter 'DO WHATIWANT' it runs fine, even with the QUIT at the end closing dbase. To take it the last step, I am trying to find out how to make DBASE III Plus automatically run a pgm file from the DOS line. I know I can use DBASE WHATIWANT to run the .pgm file, but it always stops at the initial opening of DBASE and says "press enter to assend to the license agreement and start DBASE". If I press enter before it times out in 5 seconds or so, the .pgm file runs normally. If I start DBASE with no 'filename' added, it starts without the license problem and goes straight to command mode as expected.

    I am assuming there is a command line parm I can add with the filename to fix this. Can someone point me to the DOS line syntax of DBASE? Additionally, can someone tell me how to eliminate the license prompt in that mode? If it matters, there is nothing in CONFIG.DB other than the 'STATUS=ON' line.
    Last edited by JeeperDon; 11-18-05 at 17:24.

  2. #2
    Join Date
    Oct 2005
    Posts
    178
    Quote Originally Posted by JeeperDon
    I am trying to totaly automate a simple database manipulation. If I invoke dbase then enter 'DO WHATIWANT' it runs fine, even with the QUIT at the end closing dbase. To take it the last step, I am trying to find out how to make DBASE III Plus automatically run a pgm file from the DOS line. I know I can use DBASE WHATIWANT to run the .pgm file, but it always stops at the initial opening of DBASE and says "press enter to assend to the license agreement and start DBASE". If I press enter before it times out in 5 seconds or so, the .pgm file runs normally. If I start DBASE with no 'filename' added, it starts without the license problem and goes straight to command mode as expected.

    I am assuming there is a command line parm I can add with the filename to fix this. Can someone point me to the DOS line syntax of DBASE? Additionally, can someone tell me how to eliminate the license prompt in that mode? If it matters, there is nothing in CONFIG.DB other than the 'STATUS=ON' line.
    It's been a while since I haven't programed in dbase III plus. If I remember correctly, after you completed your commands and save it as for example "mydbase.prg" you can create an autoexecbat in DOS by executing a dos command 'Edit". for example you call your DOS program as 'myprogram" you would type from C prompt c:>edit myprogram.bat
    then on the blank screen, write your text batch command as

    dBASE mydbase.prg

    save it and exit from Edit DOS mode.

    when you are back in C:> prompt, you can just type myprogram <ENTER> and your program should run straight like you wanted to

    DO you know that FOXPro 2.1 can be programed similarly as dBase III. With Foxpro 2.1 you can compile the commands to create an executable program.
    As a matter of fact, I still have one program still being used at an hospital to keep track of linen usage, still running almost for 10 years.

    I don't normally throw away my source development, if I stumbled across dbase III programs I wrote, I will get back with you with more accurate information.
    Last edited by fredservillon; 11-19-05 at 00:03.

  3. #3
    Join Date
    Nov 2005
    Posts
    2
    Quote Originally Posted by fredservillon
    ...you can create an autoexecbat in DOS by executing a dos command 'Edit"...
    Thank you for the reply, but you misunderstand the question. I know how to do all what you said. Making DOS batch files and dbase .prg files is easy and not the question. The exact thing I am looking for is any parameter options and syntax for them available when entering the DBASE command at a DOS prompt. I am also looking for any insite as to why DBASE presents the license pause at startup.

  4. #4
    Join Date
    Oct 2005
    Posts
    178
    I don't think there's an argument after the command "dbase" and bypass the licensing notation.
    I think this is the reason why I purchased Dos Foxpro 2.6 before so I could
    compile the source code and not having to see this licensing note before executing the program. The commands in dbase are compatible with DOS foxpro so you don't have to learn anything. Foxpro is faster than dbase because it can be compiled. And once you compiled the codes to *.com, you'll have a stand alone program that you can package for installation using PC Install. I still have these things I believe in my garage storage somewhere.
    Last edited by fredservillon; 11-22-05 at 22:04.

  5. #5
    Join Date
    Dec 2003
    Posts
    104
    It seems to me, that licensing thing came up if dBase was copied from an installation rather than properly installed from the original disks. I don't think you're going to get around it.
    It also seems there was a small DOS program which would enable you to get around that. I believe it was called NOKEY.COM. You would put the command NOKEY > NULL in either the config.sys or autoexec.bat as I recall.

    But when you're working with something like that which is over 20 years old now, you pretty much have to take what you get.

    If your business depends on a product to do real work, you should seriously consider spending the money to use a modern, reliable database product such as Visual Foxpro, rather than try to hack through some sort of antiquated, DOS based product which is going to do nothing but cause you grief.
    DSummZZZ

    Even more Fox stuff at
    www.davesummers.net/foxprolinks.htm

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •