dBase runs poorly on WinXP

Toggle sidebar Toggle sidebar
G

Guest

Guest
Archived from groups: microsoft.public.windowsxp.general (More info?)

I have been coding in dBase since 1982. Upgrading to Win95, 98 and ME was no
problem. But now that I have upgraded to XP on a 3.2 ghz Intel machine with
a gig of ram, I am having two serious performance problems. I am using dBase
IV 2.0.

Keyboard input is slow and sporadic to display.

Printing is delayed by up to a minute, but will execute immediatley if I
exit the program.

I have tried changing every aspet of the short cuts properties, including
compatibily option, and executing it from CMD.EXE instead of COMMAND.COM.
But nothing seems to help.

I should also note that the program performs well in full screen mode, but
not in a wondow as desired. Also changing LPT timeout value in the registry
from 15 to 3 has helped the printing issue, but a 10 to 15 second delay
remains.
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

If you can put up with software that is over 20 years old, you can put up
with a 15 second delay when printing. 🙂

"Tom Frey" wrote:

> I have been coding in dBase since 1982. Upgrading to Win95, 98 and ME was no
> problem. But now that I have upgraded to XP on a 3.2 ghz Intel machine with
> a gig of ram, I am having two serious performance problems. I am using dBase
> IV 2.0.
>
> Keyboard input is slow and sporadic to display.
>
> Printing is delayed by up to a minute, but will execute immediatley if I
> exit the program.
>
> I have tried changing every aspet of the short cuts properties, including
> compatibily option, and executing it from CMD.EXE instead of COMMAND.COM.
> But nothing seems to help.
>
> I should also note that the program performs well in full screen mode, but
> not in a wondow as desired. Also changing LPT timeout value in the registry
> from 15 to 3 has helped the printing issue, but a 10 to 15 second delay
> remains.
>
>
>
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

Tom Frey wrote:
> I have been coding in dBase since 1982. Upgrading to Win95, 98 and ME was no
> problem. But now that I have upgraded to XP on a 3.2 ghz Intel machine with
> a gig of ram, I am having two serious performance problems. I am using dBase
> IV 2.0.
>
> Keyboard input is slow and sporadic to display.
>
> Printing is delayed by up to a minute, but will execute immediatley if I
> exit the program.
>
> I have tried changing every aspet of the short cuts properties, including
> compatibily option, and executing it from CMD.EXE instead of COMMAND.COM.
> But nothing seems to help.
>
> I should also note that the program performs well in full screen mode, but
> not in a wondow as desired. Also changing LPT timeout value in the registry
> from 15 to 3 has helped the printing issue, but a 10 to 15 second delay
> remains.

dBase 2.0 is somewhat dated since the final dBase for DOS
version from Borland is 5.0 >> updated to 5.5. We are still
using it in our high-speed 3.0 GHz and faster machines, in
full-screen mode, without any issues. As for keyboard, the
best that works with it, in our experience, are genuine IBM
ones. There is no delay in printing, since our output is in
ASCII to hardware-configured LaserJet following the HP-PCL4
standard. IOW, no reliance on Windows enhancements, which
would demonstrate the problems cited in the above posting.
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

There are interfaces out there that can work with your dbf tables but may
have to use the following languages:

Delphi (object pascal)
Visual Basic
C# (borland/microsoft)
C++

The following are suppliers of the components:
advantagedatabase.com (recommended - excellent tech support & TDataset is
free!) Join the newsgroup: devzone.advantagedatabase.com
codebase.com
softsci.com (topaz)
There are more out there in webworld.

You may need to do it now or face the wrath of obsolesence :)

I have converted most of my dBase and Clipper Applications with great
success!



"Billy" <Billy@discussions.microsoft.com> wrote in message
news:9EC482AA-5D37-40E1-8E40-EEF249A6BE56@microsoft.com...
> If you can put up with software that is over 20 years old, you can put up
> with a 15 second delay when printing. 🙂
>
> "Tom Frey" wrote:
>
>> I have been coding in dBase since 1982. Upgrading to Win95, 98 and ME was
>> no
>> problem. But now that I have upgraded to XP on a 3.2 ghz Intel machine
>> with
>> a gig of ram, I am having two serious performance problems. I am using
>> dBase
>> IV 2.0.
>>
>> Keyboard input is slow and sporadic to display.
>>
>> Printing is delayed by up to a minute, but will execute immediatley if I
>> exit the program.
>>
>> I have tried changing every aspet of the short cuts properties, including
>> compatibily option, and executing it from CMD.EXE instead of COMMAND.COM.
>> But nothing seems to help.
>>
>> I should also note that the program performs well in full screen mode,
>> but
>> not in a wondow as desired. Also changing LPT timeout value in the
>> registry
>> from 15 to 3 has helped the printing issue, but a 10 to 15 second delay
>> remains.
>>
>>
>>
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

Thanks for the info, I might do that one day. In the past I have invested a
good bit of both time and money in Visual Basic, Visual C++ and Visual
Foxpro, but just don't need their complexity or functionality.

If I can get the XP dos emulator to work correctly I'll be fine. It runs the
program, so why shouldn't it run it well? It's all just ASCII, and it
doesn't do any direct screen or port writes.


"Benedictum" <benedictum@dominusvobis.com> wrote in message
news:e$0CCyhuFHA.2312@TK2MSFTNGP14.phx.gbl...
> There are interfaces out there that can work with your dbf tables but may
> have to use the following languages:
>
> Delphi (object pascal)
> Visual Basic
> C# (borland/microsoft)
> C++
>
> The following are suppliers of the components:
> advantagedatabase.com (recommended - excellent tech support & TDataset
is
> free!) Join the newsgroup: devzone.advantagedatabase.com
> codebase.com
> softsci.com (topaz)
> There are more out there in webworld.
>
> You may need to do it now or face the wrath of obsolesence :)
>
> I have converted most of my dBase and Clipper Applications with great
> success!
>
>
>
> "Billy" <Billy@discussions.microsoft.com> wrote in message
> news:9EC482AA-5D37-40E1-8E40-EEF249A6BE56@microsoft.com...
> > If you can put up with software that is over 20 years old, you can put
up
> > with a 15 second delay when printing. 🙂
> >
> > "Tom Frey" wrote:
> >
> >> I have been coding in dBase since 1982. Upgrading to Win95, 98 and ME
was
> >> no
> >> problem. But now that I have upgraded to XP on a 3.2 ghz Intel machine
> >> with
> >> a gig of ram, I am having two serious performance problems. I am using
> >> dBase
> >> IV 2.0.
> >>
> >> Keyboard input is slow and sporadic to display.
> >>
> >> Printing is delayed by up to a minute, but will execute immediatley if
I
> >> exit the program.
> >>
> >> I have tried changing every aspet of the short cuts properties,
including
> >> compatibily option, and executing it from CMD.EXE instead of
COMMAND.COM.
> >> But nothing seems to help.
> >>
> >> I should also note that the program performs well in full screen mode,
> >> but
> >> not in a wondow as desired. Also changing LPT timeout value in the
> >> registry
> >> from 15 to 3 has helped the printing issue, but a 10 to 15 second delay
> >> remains.
> >>
> >>
> >>
>
>
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

"Ghostrider" <-00-@fitron.142> wrote in message
news:umNdLoiuFHA.1256@TK2MSFTNGP09.phx.gbl...
>
> Tom Frey wrote:
> > I have been coding in dBase since 1982. Upgrading to Win95, 98 and ME
was no
> > problem. But now that I have upgraded to XP on a 3.2 ghz Intel machine
with
> > a gig of ram, I am having two serious performance problems. I am using
dBase
> > IV 2.0.
> >
> > Keyboard input is slow and sporadic to display.
> >
> > Printing is delayed by up to a minute, but will execute immediatley if I
> > exit the program.
> >
> > I have tried changing every aspet of the short cuts properties,
including
> > compatibily option, and executing it from CMD.EXE instead of
COMMAND.COM.
> > But nothing seems to help.
> >
> > I should also note that the program performs well in full screen mode,
but
> > not in a wondow as desired. Also changing LPT timeout value in the
registry
> > from 15 to 3 has helped the printing issue, but a 10 to 15 second delay
> > remains.
>
> dBase 2.0 is somewhat dated since the final dBase for DOS
> version from Borland is 5.0 >> updated to 5.5. We are still
> using it in our high-speed 3.0 GHz and faster machines, in
> full-screen mode, without any issues. As for keyboard, the
> best that works with it, in our experience, are genuine IBM
> ones. There is no delay in printing, since our output is in
> ASCII to hardware-configured LaserJet following the HP-PCL4
> standard. IOW, no reliance on Windows enhancements, which
> would demonstrate the problems cited in the above posting.

Thanks for your input. It's nice to know someone has some experience running
it for some time.

I'm using dBase 4, version 2.0. As I'm sure you know, dBase 4 was
distributed in three versions, 1.0, 1.5 and 2.0. So I'm not far behind you.
I have dBase 5 around here somewhere, but just never took time to install
it.

What print driver are you using, the Generic / Text Only? I tried it and it
seemed to help a little. Thanks for the tip.
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

Tom Frey wrote:

> "Ghostrider" <-00-@fitron.142> wrote in message
>
>>
>>dBase 2.0 is somewhat dated since the final dBase for DOS
>>version from Borland is 5.0 >> updated to 5.5. We are still
>>using it in our high-speed 3.0 GHz and faster machines, in
>>full-screen mode, without any issues. As for keyboard, the
>>best that works with it, in our experience, are genuine IBM
>>ones. There is no delay in printing, since our output is in
>>ASCII to hardware-configured LaserJet following the HP-PCL4
>>standard. IOW, no reliance on Windows enhancements, which
>>would demonstrate the problems cited in the above posting.
>
>
> Thanks for your input. It's nice to know someone has some experience running
> it for some time.
>
> I'm using dBase 4, version 2.0. As I'm sure you know, dBase 4 was
> distributed in three versions, 1.0, 1.5 and 2.0. So I'm not far behind you.
> I have dBase 5 around here somewhere, but just never took time to install
> it.
>
> What print driver are you using, the Generic / Text Only? I tried it and it
> seemed to help a little. Thanks for the tip.

Using Generic print driver in dBase. HP LaserJet printer
set up to use fixed fonts, just like an old-fashioned dot-
matrix line printer. A lot of time is wasted when the printer
must deal with Tru-Type, proportional fonts. Our usage of
dBase is strictly for generating meaningful reports out of
our number-crunching projects. HTH.
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

Why not give a try to dbase Plus for windows ?

www.dbase.com

"Tom Frey" <tomfrey2@cox.net> a écrit dans le message de news:
6RhWe.2923$P34.1588@okepread07...
>I have been coding in dBase since 1982. Upgrading to Win95, 98 and ME was
>no
> problem. But now that I have upgraded to XP on a 3.2 ghz Intel machine
> with
> a gig of ram, I am having two serious performance problems. I am using
> dBase
> IV 2.0.
>
> Keyboard input is slow and sporadic to display.
>
> Printing is delayed by up to a minute, but will execute immediatley if I
> exit the program.
>
> I have tried changing every aspet of the short cuts properties, including
> compatibily option, and executing it from CMD.EXE instead of COMMAND.COM.
> But nothing seems to help.
>
> I should also note that the program performs well in full screen mode, but
> not in a wondow as desired. Also changing LPT timeout value in the
> registry
> from 15 to 3 has helped the printing issue, but a 10 to 15 second delay
> remains.
>
>
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

"Tom Frey" <tomfrey2@cox.net> writes:
>"Ghostrider" <-00-@fitron.142> wrote in message
>> Tom Frey wrote:
>> > I have been coding in dBase since 1982. Upgrading to Win95, 98 and ME
>> dBase 2.0 is somewhat dated since the final dBase for DOS
>> version from Borland is 5.0 >> updated to 5.5. We are still
>> using it in our high-speed 3.0 GHz and faster machines, in
>> full-screen mode, without any issues.

>Thanks for your input. It's nice to know someone has some experience running
>it for some time.

My mother is still happily running dBase 3, started under dos 3 I think
and now up to WinXP. Each time an old machine fails I have to make the
trip to migrate all the stuff to the next newer machine. I don't even
recognize all the code I wrote decades ago that she still uses.
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

"Ghostrider" <-00-@fitron.142> wrote in message
news:Oi6y1PkuFHA.3500@TK2MSFTNGP09.phx.gbl...
>
>
> Tom Frey wrote:
>
> > "Ghostrider" <-00-@fitron.142> wrote in message
> >
> >>
> >>dBase 2.0 is somewhat dated since the final dBase for DOS
> >>version from Borland is 5.0 >> updated to 5.5. We are still
> >>using it in our high-speed 3.0 GHz and faster machines, in
> >>full-screen mode, without any issues. As for keyboard, the
> >>best that works with it, in our experience, are genuine IBM
> >>ones. There is no delay in printing, since our output is in
> >>ASCII to hardware-configured LaserJet following the HP-PCL4
> >>standard. IOW, no reliance on Windows enhancements, which
> >>would demonstrate the problems cited in the above posting.
> >
> >
> > Thanks for your input. It's nice to know someone has some experience
running
> > it for some time.
> >
> > I'm using dBase 4, version 2.0. As I'm sure you know, dBase 4 was
> > distributed in three versions, 1.0, 1.5 and 2.0. So I'm not far behind
you.
> > I have dBase 5 around here somewhere, but just never took time to
install
> > it.
> >
> > What print driver are you using, the Generic / Text Only? I tried it and
it
> > seemed to help a little. Thanks for the tip.
>
> Using Generic print driver in dBase. HP LaserJet printer
> set up to use fixed fonts, just like an old-fashioned dot-
> matrix line printer. A lot of time is wasted when the printer
> must deal with Tru-Type, proportional fonts. Our usage of
> dBase is strictly for generating meaningful reports out of
> our number-crunching projects. HTH.

Ok, I got ya. I always used the default printer in dBase for the same
reason. I never fiddled with fonts in dBase. I thought you meant the XP
driver. I selected the Generic/Text driver in XP and cut my print wait time
from 15 seconds to 11 seconds. It's getting a little more livable. I'm just
using a ink jet. I don't print a lot, but change forms often. That long
delay was killing me when I ship something. I have to print a packing slip,
two delivery tickets and two invoice copys so I had a cumulitive wait of
about 5 minutes. This will get it down to about a minute. Thanks again.
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

I'd like to get a good look at it. I saw their web site while looking for
answers. It's a bit pricy to buy on speculation, but I would like to catch a
good demo sometime. I bought several MS Visual products including Basic, C++
and Foxpro, but they just seem to over complicate things a bit too much for
me. It just turned out to be money wasted, and a good bit of it at that. I
realize they all provide a whole new world of functionality, but I just
simply do require it. I've been so satisfied with dBase 4, that I just
played with dBase 5 a bit, and just stuck with 4 because I was comfy, and
all my needs were met. If fact, probably the only reason I moved from 3 to 4
was it's ability to work with text files.

"Martin Lambert" <email@email.com> wrote in message
news:eVK#5hkuFHA.860@TK2MSFTNGP10.phx.gbl...
> Why not give a try to dbase Plus for windows ?
>
> www.dbase.com
>
> "Tom Frey" <tomfrey2@cox.net> a écrit dans le message de news:
> 6RhWe.2923$P34.1588@okepread07...
> >I have been coding in dBase since 1982. Upgrading to Win95, 98 and ME was
> >no
> > problem. But now that I have upgraded to XP on a 3.2 ghz Intel machine
> > with
> > a gig of ram, I am having two serious performance problems. I am using
> > dBase
> > IV 2.0.
> >
> > Keyboard input is slow and sporadic to display.
> >
> > Printing is delayed by up to a minute, but will execute immediatley if I
> > exit the program.
> >
> > I have tried changing every aspet of the short cuts properties,
including
> > compatibily option, and executing it from CMD.EXE instead of
COMMAND.COM.
> > But nothing seems to help.
> >
> > I should also note that the program performs well in full screen mode,
but
> > not in a wondow as desired. Also changing LPT timeout value in the
> > registry
> > from 15 to 3 has helped the printing issue, but a 10 to 15 second delay
> > remains.
> >
> >
>
>
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

"Don Taylor" <dont@agora.rdrop.com> wrote in message
news:XfSdndVZ88iokbfeRVn-jw@scnresearch.com...
> "Tom Frey" <tomfrey2@cox.net> writes:
> >"Ghostrider" <-00-@fitron.142> wrote in message
> >> Tom Frey wrote:
> >> > I have been coding in dBase since 1982. Upgrading to Win95, 98 and ME
> >> dBase 2.0 is somewhat dated since the final dBase for DOS
> >> version from Borland is 5.0 >> updated to 5.5. We are still
> >> using it in our high-speed 3.0 GHz and faster machines, in
> >> full-screen mode, without any issues.
>
> >Thanks for your input. It's nice to know someone has some experience
running
> >it for some time.
>
> My mother is still happily running dBase 3, started under dos 3 I think
> and now up to WinXP. Each time an old machine fails I have to make the
> trip to migrate all the stuff to the next newer machine. I don't even
> recognize all the code I wrote decades ago that she still uses.

Does dBase 3 have any display problems running in a window, or do you have
to run it in full screen mode? And are you experiencing any print delays?
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

"Tom Frey" <tomfrey2@cox.net> writes:
>"Don Taylor" <dont@agora.rdrop.com> wrote in message
>> My mother is still happily running dBase 3, started under dos 3 I think
>> and now up to WinXP. Each time an old machine fails I have to make the
>> trip to migrate all the stuff to the next newer machine. I don't even
>> recognize all the code I wrote decades ago that she still uses.

>Does dBase 3 have any display problems running in a window, or do you have
>to run it in full screen mode? And are you experiencing any print delays?

I honestly don't remember. I'd have to ask. But I do not recall either
of the problems that you describe when I moved it over to XP and did my
usual testing of the stuff I wrote.
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

Have you tried bypassing the spooler in printer Properties, Advanced,
print directly?

Tom Frey wrote:

> "Ghostrider" <-00-@fitron.142> wrote in message
> news:Oi6y1PkuFHA.3500@TK2MSFTNGP09.phx.gbl...
>
>>
>>Tom Frey wrote:
>>
>>
>>>"Ghostrider" <-00-@fitron.142> wrote in message
>>>
>>>
>>>>dBase 2.0 is somewhat dated since the final dBase for DOS
>>>>version from Borland is 5.0 >> updated to 5.5. We are still
>>>>using it in our high-speed 3.0 GHz and faster machines, in
>>>>full-screen mode, without any issues. As for keyboard, the
>>>>best that works with it, in our experience, are genuine IBM
>>>>ones. There is no delay in printing, since our output is in
>>>>ASCII to hardware-configured LaserJet following the HP-PCL4
>>>>standard. IOW, no reliance on Windows enhancements, which
>>>>would demonstrate the problems cited in the above posting.
>>>
>>>
>>>Thanks for your input. It's nice to know someone has some experience
>
> running
>
>>>it for some time.
>>>
>>>I'm using dBase 4, version 2.0. As I'm sure you know, dBase 4 was
>>>distributed in three versions, 1.0, 1.5 and 2.0. So I'm not far behind
>
> you.
>
>>>I have dBase 5 around here somewhere, but just never took time to
>
> install
>
>>>it.
>>>
>>>What print driver are you using, the Generic / Text Only? I tried it and
>
> it
>
>>>seemed to help a little. Thanks for the tip.
>>
>>Using Generic print driver in dBase. HP LaserJet printer
>>set up to use fixed fonts, just like an old-fashioned dot-
>>matrix line printer. A lot of time is wasted when the printer
>>must deal with Tru-Type, proportional fonts. Our usage of
>>dBase is strictly for generating meaningful reports out of
>>our number-crunching projects. HTH.
>
>
> Ok, I got ya. I always used the default printer in dBase for the same
> reason. I never fiddled with fonts in dBase. I thought you meant the XP
> driver. I selected the Generic/Text driver in XP and cut my print wait time
> from 15 seconds to 11 seconds. It's getting a little more livable. I'm just
> using a ink jet. I don't print a lot, but change forms often. That long
> delay was killing me when I ship something. I have to print a packing slip,
> two delivery tickets and two invoice copys so I had a cumulitive wait of
> about 5 minutes. This will get it down to about a minute. Thanks again.
>
>
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

Yes, surprisingly it did seem to make any difference on my machine. But
printing with XP's Generic/Text driver, instead of the HP driver, did cut it
about 4 seconds or so.

"Bob I" <birelan@yahoo.com> wrote in message
news:uTUTVasuFHA.3500@TK2MSFTNGP09.phx.gbl...
> Have you tried bypassing the spooler in printer Properties, Advanced,
> print directly?
>
> Tom Frey wrote:
>
> > "Ghostrider" <-00-@fitron.142> wrote in message
> > news:Oi6y1PkuFHA.3500@TK2MSFTNGP09.phx.gbl...
> >
> >>
> >>Tom Frey wrote:
> >>
> >>
> >>>"Ghostrider" <-00-@fitron.142> wrote in message
> >>>
> >>>
> >>>>dBase 2.0 is somewhat dated since the final dBase for DOS
> >>>>version from Borland is 5.0 >> updated to 5.5. We are still
> >>>>using it in our high-speed 3.0 GHz and faster machines, in
> >>>>full-screen mode, without any issues. As for keyboard, the
> >>>>best that works with it, in our experience, are genuine IBM
> >>>>ones. There is no delay in printing, since our output is in
> >>>>ASCII to hardware-configured LaserJet following the HP-PCL4
> >>>>standard. IOW, no reliance on Windows enhancements, which
> >>>>would demonstrate the problems cited in the above posting.
> >>>
> >>>
> >>>Thanks for your input. It's nice to know someone has some experience
> >
> > running
> >
> >>>it for some time.
> >>>
> >>>I'm using dBase 4, version 2.0. As I'm sure you know, dBase 4 was
> >>>distributed in three versions, 1.0, 1.5 and 2.0. So I'm not far behind
> >
> > you.
> >
> >>>I have dBase 5 around here somewhere, but just never took time to
> >
> > install
> >
> >>>it.
> >>>
> >>>What print driver are you using, the Generic / Text Only? I tried it
and
> >
> > it
> >
> >>>seemed to help a little. Thanks for the tip.
> >>
> >>Using Generic print driver in dBase. HP LaserJet printer
> >>set up to use fixed fonts, just like an old-fashioned dot-
> >>matrix line printer. A lot of time is wasted when the printer
> >>must deal with Tru-Type, proportional fonts. Our usage of
> >>dBase is strictly for generating meaningful reports out of
> >>our number-crunching projects. HTH.
> >
> >
> > Ok, I got ya. I always used the default printer in dBase for the same
> > reason. I never fiddled with fonts in dBase. I thought you meant the XP
> > driver. I selected the Generic/Text driver in XP and cut my print wait
time
> > from 15 seconds to 11 seconds. It's getting a little more livable. I'm
just
> > using a ink jet. I don't print a lot, but change forms often. That long
> > delay was killing me when I ship something. I have to print a packing
slip,
> > two delivery tickets and two invoice copys so I had a cumulitive wait of
> > about 5 minutes. This will get it down to about a minute. Thanks again.
> >
> >
>
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

"Don Taylor" <dont@agora.rdrop.com> wrote in message
news:cYOdnewzSJen87feRVn-2A@scnresearch.com...
> "Tom Frey" <tomfrey2@cox.net> writes:
> >"Don Taylor" <dont@agora.rdrop.com> wrote in message
> >> My mother is still happily running dBase 3, started under dos 3 I think
> >> and now up to WinXP. Each time an old machine fails I have to make the
> >> trip to migrate all the stuff to the next newer machine. I don't even
> >> recognize all the code I wrote decades ago that she still uses.
>
> >Does dBase 3 have any display problems running in a window, or do you
have
> >to run it in full screen mode? And are you experiencing any print delays?
>
> I honestly don't remember. I'd have to ask. But I do not recall either
> of the problems that you describe when I moved it over to XP and did my
> usual testing of the stuff I wrote.

Check it out when you get a chance, no hurry. Let me know on direct. I'm not
sure how much longer I will monitoring this post.
 
Archived from groups: microsoft.public.windowsxp.general (More info?)

"Ghostrider" <-00-@fitron.142> wrote in message
news:Oi6y1PkuFHA.3500@TK2MSFTNGP09.phx.gbl...
>
>
> Tom Frey wrote:
>
> > "Ghostrider" <-00-@fitron.142> wrote in message
> >
> >>
> >>dBase 2.0 is somewhat dated since the final dBase for DOS
> >>version from Borland is 5.0 >> updated to 5.5. We are still
> >>using it in our high-speed 3.0 GHz and faster machines, in
> >>full-screen mode, without any issues. As for keyboard, the
> >>best that works with it, in our experience, are genuine IBM
> >>ones. There is no delay in printing, since our output is in
> >>ASCII to hardware-configured LaserJet following the HP-PCL4
> >>standard. IOW, no reliance on Windows enhancements, which
> >>would demonstrate the problems cited in the above posting.
> >
> >
> > Thanks for your input. It's nice to know someone has some experience
running
> > it for some time.
> >
> > I'm using dBase 4, version 2.0. As I'm sure you know, dBase 4 was
> > distributed in three versions, 1.0, 1.5 and 2.0. So I'm not far behind
you.
> > I have dBase 5 around here somewhere, but just never took time to
install
> > it.
> >
> > What print driver are you using, the Generic / Text Only? I tried it and
it
> > seemed to help a little. Thanks for the tip.
>
> Using Generic print driver in dBase. HP LaserJet printer
> set up to use fixed fonts, just like an old-fashioned dot-
> matrix line printer. A lot of time is wasted when the printer
> must deal with Tru-Type, proportional fonts. Our usage of
> dBase is strictly for generating meaningful reports out of
> our number-crunching projects. HTH.

Do you experience display problems with Visual dBase when you run it in a XP
window?
 
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom