Search found 32 matches

by dougtanner
Fri May 04, 2012 5:14 am
Forum: Xbase++ Support
Topic: Slow Printing in Alaska
Replies: 6
Views: 12779

Re: Slow Printing in Alaska

Roger,

I submitted my issue to Alaska Support. I'll let you know if I hear anything back.

Auge_Ohr,

I eliminated the PROW() and PCOL() function calls and the printing was just as slow. The issue must be imbedded in the DevOut() function. Thanks for the suggestion.

Doug
by dougtanner
Thu May 03, 2012 1:00 pm
Forum: Xbase++ Support
Topic: Slow Printing in Alaska
Replies: 6
Views: 12779

Slow Printing in Alaska

I have several large applications That print several hundred documents of 100 to 600 pages in length. All of the printing is done to a file with imbedded PCL commands and sent though a document handling system to our high speed printers. We print over 2,000,000 sheets a month. Alaska is taking 10 ti...
by dougtanner
Wed Apr 25, 2012 12:56 pm
Forum: eXpress++ Support
Topic: Slow Printing
Replies: 1
Views: 4737

Slow Printing

I am converting several reporting system applications from Clipper 5.2 to Alaska. Printing reports are the form: SET PRINTER TO (afile) SET DEVICE TO PRINTER 300 to 400 pages of @ Says SET PRINTER TO SET DEVICE TO SCREEN This took 20 Minutes in Clipper, it is taking an hour and 20 minutes in Alaska....
by dougtanner
Tue Apr 10, 2012 8:05 am
Forum: Xbase++ Support
Topic: Clipper Incompatible CDX Indexs
Replies: 3
Views: 9198

Re: Clipper Incompatible CDX Indexs

Roger,

Yes I am. The SIX CDX Drivers were the only ones that worked reliably in several of my applications.

Auge_Uhr,

I will try that in my DBWSys

Doug
by dougtanner
Mon Apr 09, 2012 10:22 am
Forum: Xbase++ Support
Topic: Clipper Incompatible CDX Indexs
Replies: 3
Views: 9198

Clipper Incompatible CDX Indexs

I am converting several large system from Clipper 5.2 to Alaska. I am having a problem if xBase++ creates a CDX Index, it is incompatible with Clipper. Clipper will crash with a memory exception and dump its registers. When I delete the Indexes and let Clipper create them, both Clipper and xBase++ r...
by dougtanner
Tue Apr 03, 2012 8:35 am
Forum: Xbase++ Support
Topic: DBZAP() Corrupted
Replies: 10
Views: 21449

Re: DBZAP() Corrupted

Thanks Tom, There must be some size point where a DBF SEEK is faster than and ASCAN() for temporary information. But I agree that array's are a better solution for temporary data. However, I have lots of Old Code that works and was created during a time that memory was not so available. So my soluti...
by dougtanner
Tue Apr 03, 2012 6:37 am
Forum: Xbase++ Support
Topic: DBZAP() Corrupted
Replies: 10
Views: 21449

Re: DBZAP() Corrupted

I was premature in thinking the problem was fixed. It went from happening frequently to happening every now and then. It looks like I will rewrite the code to eliminate the Zaps!

Doug
by dougtanner
Mon Apr 02, 2012 10:50 am
Forum: Xbase++ Support
Topic: DBZAP() Corrupted
Replies: 10
Views: 21449

Re: DBZAP() Corrupted

Roger,

The close and reopen function stopped the stopped the IDSC errors for DBZAP()

Thanks,
Doug
by dougtanner
Mon Apr 02, 2012 8:40 am
Forum: Xbase++ Support
Topic: DBZAP() Corrupted
Replies: 10
Views: 21449

Re: DBZAP() Corrupted

Roger, I changed: USE (cDBF) EXCLUSIVE VIA (cAlias) TO: USE (cDBF) EXCLUSIVE ALIAS (cAlias) Which worked, You were just testing me weren't you? After second thoughts, to be safe, I changed it to IF ".CDX" $ cIndex USE (cDBF) EXCLUSIVE ALIAS (cAlias) VIA "DBFCDX" ELSE USE (cDBF) EXCLUSIVE ALIAS (cAli...
by dougtanner
Mon Apr 02, 2012 7:50 am
Forum: Xbase++ Support
Topic: DBZAP() Corrupted
Replies: 10
Views: 21449

Re: DBZAP() Corrupted

Jimmy, I tried putting the files on both places, Local hard drive and on the Windows server. Same intermittent error. The OS was Windows XP. The files had been in exclusive use and Zap'ed several times before the error. Rodger, I like your solution and had already figured out that closing and recrea...