DBase III+ under XP Professional

[swamprabbit]

I am new to the forum. In 1986, I bought a Kaypro computer running CPM and, for software, bought Wordstar and DBase. Using DBase's programming language, I wrote my own accounting system. When DOS came along, I converted to DOS. When Windows 95 came along, I converted to that. After several DBase versions, I finally settled on DBase III+ as the most useful to me, and I have been running it as a DOS app (along with Wordstar 6.0) ever since. Both ran successfully under Win95, Win98, Win 2000 Pro and, most recently, under XP Professional, v. 2002, Service Pack 1. Both run full screen, which is what I prefer.

I always run two computers, one for the net and one for work, to avoid corrupting my work files. On 5/30/03, I bought a new Net computer running XP Pro v. 2002, w/SP 1. It has an Intel 2.4GH processor and a 250GB hard drive, among other attributes. It runs both Wordstar and Dbase III+ as DOS apps full screen just fine. The only fault I have with it is the monitor sometimes blanks and has to be turned off and then on again to work. My techs (the ones who sold me the computer) can't seem to fix that.

On January 15, 2004, I bought a new work computer. It has a 2.79GHz Intel Xeon processor, a 120GB hard drive and is running Windows XP Professional, v. 2002, Service Pack 1.

MY PROBLEM: The new computer will run Wordstar full screen just fine, but will only run DBase III+ in a window. When I try to run it full screen, it gives me a black screen with a blinking while cursor in the upper left-hand corner, and I cannot exit without using the task manager. I have tried everything I know and the service techs here have tried everything, including fooling with the compatibility settings in Properties. Nothing works. The only thing I haven't tried to change is the buffer size, which is 50, and the number of buffers is 4.

What am I complaining about, you ask? Why not run DBase in a window?

When I run it in the window, there is some kind of lag between keystrokes and the screen, so that I end up with a lot of typo errors, like characters being typed on top of one another, forcing me to back up and correct them. It is a real hassle and slows my work substantially.

I could swap the Net and work computers, but I would not like to do that unless all else fails.

I have noticed that, although the operating systems tell me they are the same, the newer computer has a slightly different "Properties" pane than the one running on the Net computer. The compatability tab is slightly different, although it seems to offer the same choices. Could that be the problem?

One of the techs here has suggested that the problems lies with the processor.

Until I am driven to it, I do not plan to "upgrade" from DBase III+ to some kind of Windows database, for fear I won't be able to write all those utilities I routinely write daily to help manipulate the database. I have written literally thousands of programs in DBase for my accounting system, and I use DBase daily. I do not consider myself a programmer, but an enduser. I just like to write programs because it helps me in my work. I am an engineer, by the way, with an M.S. Most 17 year old kids, however, know more about computers than I do.

Any suggestions out there?

 

[tviman]

I tend to think like your tech guys in that the problem lies in the processor speed. Basically, the dBase can't keep up with the processor. I've heard that there are utilities that can slow the processor but I've never used them so I can't vouch for them. Of course, you could always buy a used PC running Win98 and dedicate it to your dBase software.

To be honest, you should think about switching to a Windows based program like Access or Visual FoxPro. I'm going to bet that the next time you upgrade to a 4ghz processor, you won't be able to get dBase to run at all.

There's always a better way. The fun is trying to find it!

 

[swamprabbit]

Thank you for your valuable and insightful comment in response to my problem with DBase III+.

You suggest upgrading to Access or Visual Fox Pro. Will I be able to write my utilities in either of these as I have been doing in DBase III+? What kind of learning curve will I encounter in switching? Here is an example of code I wrote several years ago to reconcile a bank account:

"clear
set safety off
set talk off
text

RECONCILE.PRG

This program helps reconcile a bank balance. It first asks for the name of the accounting file, such as “HSFAC89”. Next, it asks for the end of period bank statement balance and the end of the period date in the form “01/31/89”, for “January 31, 1989”, after which it asks for your book balance. It next asks for cleared checks, which are entered one at a time. The program operates on the “CLEARED” field in the database to insert a “Y” for each check as it clears. To reconcile the account, the program merely adds all checks which do not have a “Y” in the cleared filed and deducts this figure to the ending bank statement balance. Next, it totals the amount received column for transactions with an amount in the amtrecd field, a zero in the amt paid field and a date_dep later than the end of period date to obtain the sum of checks dated before the end of period date but deposited afterwards. That total is then added to the adjusted end of period bank statement balance to produce the ending book balance. The two are displayed for comparison. Eliminate any extraneous dates of deposit from the DATE DEP field or the program will not work properly. Always put a “99” in the check_no field of unpaid credit transactions such as VISA and other ACCOUNTS PAYABLE transactions.
endtext
store 0 to u store 0 to y @ 23,0 say restore from chexvars
accept “File to be reconciled: “ to file save to chexvars
use &file
replace cleared with ‘Y’ for check no=l0 clear
disp date,item,checkno,amtpaid,cleared for check no=0 .and. amtpa id<>0
@ 18,0 clear @18,Osay’
wait “These are the debit memos. O.K. to clear (Y/N)? “ to d store upper (“&d”) to d
if d=’N’
return
else
replace cleared with ‘Y’ for amtpaid<>0 .and. check no=0 end if
restore from chexvars locate for account<>’ store account to axe set catalog of f save to chexvars copy structure to ychex copy structure to uchex store ‘ ‘ to rex"

Only the first page of the program in included. I don't wish to post the entire program on the net. You get the idea, though. I realize the name has more than 8 characters, but DBase doesn't seem to mind.

Will I be able to write code like this with FoxPro? Access?

If you could suggest any books or websites which might be helpful, I would appreciate it.

 

[1oldfoxman]

For the most part, you programs will run in Foxpro (at least v6 which I'm more familiar with). Some minor syntax changes will be necessary (UPPER("&d")generated an error, I believe it's probably UPPER(d)instead), and the screen input (@say .... get.....) can be klugy in an object-oriented product. All your data handling commands will work just fine.

Funny, I'm an engineer (with an MBA instead, though) who's used dBaseIII+ for thousands of programs as well. FoxPro is a lot better for applications however if you'll take the time to learn the basics. Even just against your existing code it will run WAY faster, especially if the indexes are optimizable in Fox's Rushmore indexing technology. Clearly it's more costly though, and may be overkill for what you're doing.

hth
dennis

 

[swamprabbit]

Thanks for your help. I agree with you. For my purposes, Fox Pro is probably overkill. I do not program for the joy of the challenge, or to learn more about programming and computers. I do it to help me be more productive in what I do. I do not, therefore, look forward with eager anticipation to what I perceive to be the Fox Pro learning curve. My problem is that I just don't know enough about Fox Pro to be able to evaluate it without spending a lot of money, only to find out that the program is not satsifactory for my needs. I have been down that road before. An example is OmniPage 12.0. I bought PaperPort Deluxe 9.0, and liked it so much I decided to get OmniPage as well. I found I didn't need it, and never use it. But I use PaperPort daily. I am moving toward a paperless office, at least partially, and I have found PaperPort to be excellent for my purposes.

DBase has really been a big help to me. It saddens me to think one day I may have to give it up. Perhaps I will get lucky and it will outlast me (?). Just kidding, but, at my age, it is certainly possible.

I am becoming more and more convinced that the processor on my work computer is just too fast for DBase. I still have questions about why DBase will run in a window but not full screen. I suppose my understanding of how the two differ is insufficient for that purpose. Is it the speed of the processor that causes the "jerky" movement, or "lag", between keystrokes and screen? Or is it just some change in XP between the edition extant in early 2003 and the current version, even though both are v. 2002 and both are Service Pack 1?

 

[MiggyD]

Out of curiosity, have you tried pressing ALT+ENTER keys together when your dbase is running in a window?

--MiggyD

 

[swamprabbit]

Thanks for your suggestion, MiggyD.

I tried [ALT]/ENTER on my work computer, w/2.79GHz Intel Xeon processor, and it did produce a full screen. The full screen looked different from the full screen on past computers, including my current net computer, which has an Intel 2.4GHz processor.

The full screen locked my computer. I tried it again three or four times in different ways to be sure, but got the same result. The best I could do was a carriage return, which it executed, and then entry of a single digit at the dot prompt, which it allowed. After that, it locked up and I had to use Task Manager to get out of DBase. One definition of insanity, I am told, is repeating the same behavior expecting a different result. Guess I passed (or flunked, whichever is appropriate in the circumstances) that test.

What am I doing wrong?

 

[dbMark]

In this thread290-590977 are some links to others' complaints of slow computers. The top culprits are: accessing through network not local drives, certain antivirus programs, different Service Pack, and yes, CPU speed.

I have dBase for DOS 5.0 networked on CPUs up to 2.6GHz with only the usual DOS/Windows issues (where they are ignorant of each other).

Don't forget to see if there are any suggestions or fixes mentioned in other DOS database forums such as FoxPro forum182.

I saw lots of good comments about TameDOS which can be found at

http://www.tamedos.com.

Also, thread182-717271 mentions both TameDOS and DOSIDLE.COM.

dbMark

 

[swamprabbit]

dbMark:

Thanks for your valuable suggestions. I will check them out. Your comment about Tamedos is interesting; I will know more when I find out what it is. My guess is that it is software that assists in running DOS programs under Windows. When I know more, I will get back to you via the forum.

 

[MiggyD]

Sorry for the late response, swamprabbit. I'm sorry to hear that the pressing the 'maximize' keystrokes locks up your system.

I do have another query, since it wasn't asked nor mentioned above. Have you tried running your db directly from the "DOS" command prompt?

You should be able to access it [the command prompt] by clicking START > RUN then type: CMD and press enter...NOTE: if this is running in a window, I'd suggest you ALT+Enter first...use DOS's chdir [CD] command to move to the DB.EXE directory and run try running DB3+ that way.

Let us know what happens.

--MiggyD

 

[swamprabbit]

MiggyD:

Thanks for your prompt and kind response. Unfortunately, I have already tried your suggestion early in the game, when I couldn't get DBase III+ to run full screen under Windows XP on my offline computer with Intel Xeon 2.79GHz dual processor.

On my desktop, I have an icon labeled "MSDOS Prompt", which has the target C:\WINDOWS\SYSTEM32\cmd.exe. I ran both this and your suggestion. Both are the same, of course, just different ways of arriving at the same result. Didn't work. Got a blank black screen, blinking white cursor, upper lefthand corner. Locked up. Had to use Task Manager to get out of it.

Since it does not run in a window, employing ALT+ENTER first cannot help -- the keyboard will not accept input.

Thanks, anyway.

 

[MiggyD]

Sorry to hear that that too failed.

I'm out of suggestions on trying to find a "path of least resistance". As for the monitor blanking out I'm sure your techs tried changing CMOS & Windows' Display properties & Screen saver's 'energy star' properties.

Guess you'll have to try either swapping the computers or use a more "modern" windows language.

Good luck in your task.
--MiggyD

 

[swamprabbit]

MiggyD:

Thanks for your thoughts. My guess about the monitor is that the complex "Fish" screen saver I am running could be the culprit. I bought it before I upgraded to XP Pro, and I may need to upgrrade the software if I want to continue using it. It came from Sight N' Sound, if I am not mistaken. I notice that, at times, when it is invoked, I only get the aquarium sounds, but not the picture. When it runs, which is about half the time, it looks great.

I noticed the screen lockup occurred after the screen saver is activated by the timer. So I have substituted a "blank screen" screen saver for the Fish SS. It seems to be working, but I want to give it a day or two to see if the screen saver software is really the source of the problem.

To their credit, my techs have advised me that they have already ordered a replacement monitor -- I had to head them off until I could determine if it is a software, not a hardware, problem. But their zeal to help their customer is certainly admirable, don't you agree?

Keep me posted.

 

[MiggyD]

"To their credit, my techs have advised me that they have already ordered a replacement monitor -- I had to head them off until I could determine if it is a software, not a hardware, problem."

<Snickering>They must be newbie-techies...maybe swamprabbit should charge them for consultation fees?</Snickering>

"But their zeal to help their customer is certainly admirable, don't you agree?"

Yes, their zeal is admirable; however it can also be construded as hasty...they're too quick to dismiss the problem as a "monitor" problem; I think. Based on the fact that you

Got a blank black screen, blinking white cursor, upper lefthand corner.

The simple fact that the cursor IS!! blinking indicates that the monitor, itself, IS!! working. This means they need to look elsewhere.

Another thing they could check into is the video card. It may be set to (let's just say) 65hz instead of 75hz or maybe it needs to be 'adapter default/optimal'

HOWEVER; your problem stems from only 1 program and not all. So, I, personally, would side more with the problem being a software issue and not hardware.


On another matter, I'm glad to have sparked a thought in you about the screensaver. Obviously, your testing results may be of value to future members. So please keep us apprised. I'm sure, if that is the culprit, it would make us both laugh.

<thinking to self>Well maybe not you, swamprabbit, if you had to pay your techies.</thinking to self>

Keep us posted.
--MiggyD

 

[swamprabbit]

MiggyD:

Thanks for your E-Mail and informative, if somewhat cynical, comments about my techies. You will be please to know they did not charge me.

And, it is time to start laughing, because it WAS the screensaver. Since I have switched to a "blank screen" SS, there has been NO recurrence of the monitor lockup problem. I am sure Sight N Sound has a fix for the lockup problem, and the problem is most likely traceable to the Windows upgrade from Win98 to XL Pro. For the time being, however, I don't have the time nor inclination to seek an upgrade -- I will stay with the blank screen SS.

One correction -- when the screen locked up, it did not have a blinking cursor in the upper lefthand corner. The screen just went white with nothing on it. It was locked and could only be unlocked by turning the monitor off and then back on. (Cold boot?). And, the monitor was on my ONLINE computer.

The monitor on my OFFLINE computer did indeed lock up, but only when I tried running DBase III+ full screen (I do not run the "Fish" screensaver on my offline computer). Then it went all black, with a blinking white cursor in the upper lefthand corner. For the reasons you gave, I never considered the offline monitor to be the culprit. And, the problem could be corrected without restarting the monitor -- task manager was equal to the task (pun intended).

Hope my experience is helpful to those with lockup problems. The teaching is, as we have seen before, I am sure, look for the problem first in the software. Of course, here, the TYPE of lockup of the online monitor suggested the monitor possibly could be the culprit. By applying the teaching, however, we avoided foolish replacement of a perfectly functioning monitor. Those who do not learn from the mistakes of history are doomed to repeat them.

 

[swamprabbit]

Additional note to MiggyD:

Platitudes can sometimes produce strange results. I have already said, and you took note of it, that repeating the same behavior expecting a different result is one sign of insanity. That was a sort of humorous platitude.

My second platitude was that those who don't learn from the lessons of history are doomed to repeat them. That was a more serious platitude (sometimes used by high school history teachers in an attempt to stimulate flagging interest).

Now, if you put those two platitudes together, do you get: Those who don't learn from the lessons of history and repeat them might be insane?

Any logicians out there (who have time for this nonsense)?

 

[MiggyD]

Another late response, I've been busy with work and family. Your surmised theory

Those who don't learn from the lessons of history and repeat them might be insane?

had me laughing aloud.

Your techies, obviously, have great intensions by offering to order a “new” monitor, as well as, being very generous in not charging you for their services. I’m glad you found it was the screen saver’s fault and not something more costly.

I was a little harsh, I'll admit; but this is due to my experiences. Every so often the higher-ups where I work will hire an outside computer company to do something(s) to the network without consulting me—I personally believe they purposefully create problems just because there aren't any—then every department head will call me to fix the problems that were caused by these companies. This may seem misdirected—I should blame the higher-ups—but if these companies would simply ask me about the network’s setup, we can preclude any future issues and dilemmas.

Well, at least you have gotten one computer [OnLine] to work properly.

[highlight]<Start Insanity>[/highlight]

In regards to the continued keyboard “typematic” problem [OffLine], have you or your techs tried changing the “Keyboard Properties” in the Control Panel? I know that this particular setting is for Windows’ programs but it couldn’t hurt. Or maybe try changing the settings in the CMOS?

As for the blinking cursor [OffLine], it sounds like either a memory glitch or video card problem. So, have you already tried to increase FILES and BUFFERS? Are you sure that monitor’s refresh rate is set to “adapter default” or “optimal”?

[highlight]<End Insanity>[/highlight]

--MiggyD

 

[charlesdenver]

i just ran the text prrtion of your program, worked fine (full screen).
the syntex is incorrect for the rest of it ??
i'm using XP home with an 2.20 processer.
Try setting your compatability setting???.
Mine is NOT set.
a word to the wise- the best way to outsmart yourself is to assume you, or your friend, is a 'Power user'. Beware.
I have programs i've been useing since dos 3.0 and they work just fine, As Is.
Hope i helped;
Charlesdenver@msn.com

 

[cfneumann]

You should look at dBase Plus instead of Foxpro or Access. Go to dBase' site

http://dbase.com

and select the dBase SE version. This should reduce the need to totally learn a new language and you will be able to maintain the stability and robustness of dBase!!

Christopher F. Neumann
[dBASE Charter Member]
IWA-HWG Member
Blue Star Visual dBASE graduate
ICCP TCP/IP Network Analyst
Data Communications Engineer

http://cfneumann.us

 

[swamprabbit]

To charlesdenver:

Thanks for your confirmation of the integrity of my code (I only included the first part of the program), and please accept my apologies for being tardy getting back to you.

I am running XP Professional, and I can run my code, too, but only in a window. I can't run it full screen. That is the rub. Running in a window, it is not as easy to use as full screen, and I have not yet adapted very well to working with it in a window. Strangely, it runs just fine full screen on a similar machine next to it, both running Windows XP Pro, Service Pack 1. The processor on the "work computer", which is a little faster, appears to be the problem. I have tried changing the compatability settings, but that hasn't helped. Thanks for your interest and encouragement, though.