Page 6 of 6
Re: ADORDD FAQs
Posted: Sun May 15, 2016 10:10 am
by gautxori
Antonio Linares wrote:Problema solucionado
Al final de AdoRdd.prg hay una serie de funciones de FWH repetidas, que hay que eliminar.
Gracias por todo Antonio
Re: ADORDD FAQs
Posted: Mon Jul 25, 2016 8:02 pm
by aferra
I can not use hb_AdoUpload () shows the error in this line
Error DBCMD/1015 Argument error: DBUSEAREA
Stack Calls
===========
Called from: => DBUSEAREA( 0 )
Called from: D:\ADVRDD\PRG\CLASSES\adordd.prg => HB_ADOUPLOAD( 6394 )
calling program is in this way.
hb_AdoUpload ("D:\ADVSYS\DATA\", "DBFCDX", "MYSQL" .F.)
Re: ADORDD FAQs
Posted: Mon Jul 25, 2016 8:10 pm
by karinha
Re: ADORDD FAQs
Posted: Tue Jul 26, 2016 2:21 pm
by aferra
Thank you buddy, no reference to the problem.
Re: ADORDD FAQs
Posted: Tue Jul 26, 2016 2:26 pm
by karinha
Re: ADORDD FAQs
Posted: Tue Jul 26, 2016 3:08 pm
by aferra
I already downloaded the files, the problem is I can not do the conversion of the .dbf files to SQL
Re: ADORDD FAQs
Posted: Tue Jul 26, 2016 4:14 pm
by James Bott
When I open big tables several times during app execution doesn't this lead to
out of memory or very slow opening of that table?
Adordd builds each table recordset only once.
If your table recordsets have million of records you will need enough memory for it and it can easily
reach some hundred MB or more.
When you open that table again the memory consumption its minimum as adordd clones that table set, which
means a kind of pointer to previous open recordset being extremely fast opening it again and very
low on memory use.
I am not clear on this. If every user has their own copy of all the databases in memory, then how do those databases get updated in real time when other users change them? If this doesn't happen, then how can this design be useful?
James
Re: ADORDD FAQs
Posted: Tue Jul 26, 2016 9:56 pm
by James Bott
Aferra,
hb_AdoUpload ("D:\ADVSYS\DATA\", "DBFCDX", "MYSQL" .F.)
You are missing a comma before the last parameter. It should be:
hb_AdoUpload ("D:\ADVSYS\DATA\", "DBFCDX", "MYSQL", .F.)
James
Re: ADORDD FAQs
Posted: Wed Jul 27, 2016 11:09 am
by aferra
Thanks James
still gives the error
Re: ADORDD FAQs
Posted: Wed Jul 27, 2016 3:50 pm
by James Bott
Arerra,
The error message you posted before is occurring in the second line here (6394 in ADORDD.PRG):
if lOverWrite
hb_adoRddDrop( oCn, cBaseDir + aFile[ F_NAME ], , , DBEngine ) // erroring here
endif
But since you are passing .f. for lOverwrite, that line is not being executed, so it must be showing a different error message now. Please post the new error message.
James
Re: ADORDD FAQs
Posted: Fri Jul 29, 2016 2:25 pm
by aferra
ThankĀ“s James
after thinking a lot, put this information in the main.prg and oh yes right gave the upload.
REQUEST DBFNTX
REQUEST DBFDBT
REQUEST DBFCDX
REQUEST DBFFPT
REQUEST ORDKEYNO
REQUEST ORDKEYCOUNT
REQUEST ORDKEYGOTO
REQUEST DESCEND
thank you for your attention
Re: ADORDD FAQs
Posted: Fri Jul 29, 2016 2:53 pm
by James Bott
Aferra,
Thanks for posting your solution. I am going to put that in my notes.
James
Re: ADORDD FAQs
Posted: Fri Jul 29, 2016 3:46 pm
by James Bott
Temporary Indexes
From the manual:
Indicates the names used for temporary files at SQL level.
It must start by TMP or TEMP but can be "TMPROGER"
These temporary files are mainly used for temporary indexes created in the SQL server as TEMPORARY and automatically destroyed after connection ends.
I am not sure what the above means.
I have a program that generates unique filenames for temp indexes, based on what existing temp names already exist. So, there is no way to know what those filenames will be until the program is running.
It is not clear to me if the TMP and TEMP are just prefixes for filenames (like TEMP001.CDX) or if that is the complete filename. Or, do I have to specify all of the exact filenames that will be used for temp indexes? When you have 5-10 users that all have to generate multiple temp indexes, I'm not sure how exact filenames can be known before compiling the program.
Any hints on how I can resolve this will be appreciated.
James