>>>"Could not create temporary file: GenDBC.tmp ", This is driving me crazy, if someone can help me would be apreciated it.
>>
>>Try running in ADMIN mode...
>>
>>...also you might want to use GenDBCX which you can get from here http://leafe.com/download/gendbcx.zip -- it's better than the GenDBC.
>
>i used it in the past, but now i have errors like this:
>
>"CREATE TABLE command line length exceeded, using
>ALTER TABLE to add remaining fields for table CONFIGURACION_GENERAL"

Now I remember why I had to write my own generator :). It's quite possible to have a table where the total length of the create table command, with just field names and types, even without extra clauses (like defaults etc), can be more than the max command line length. Which is why I had to generate code like

 Procedure MakeTable_T_SEMENBASE
** generated by DbUpdate v1.1  [2002.11.27 18:19:40] dragan  06.07.07 13:28:17

	DIMENSION laStru[218, 18]
	laStru[1,1]="CHARField1"
laStru[1,2]="C"
laStru[1,3]=10
laStru[1,4]=0
laStru[1,5]=.T.
laStru[1,7]=""
laStru[1,8]=""
laStru[1,9]=""
laStru[1,10]=""
laStru[1,11]=""
laStru[1,12]="tablename_here"
laStru[1,13]="_RiHandl("+Chr(34)+"Ins_"+Chr(34)+")"
laStru[1,14]="_RiHandl("+Chr(34)+"Upd_"+Chr(34)+")"
laStru[1,15]=""
laStru[1,16]=""
laStru[1,17]=0
laStru[1,18]=0

And so on... a couple of thousand lines later it finally gets to

laStru[218,1]="field218"
laStru[218,2]="C"
laStru[218,3]=15
laStru[218,4]=0
laStru[218,7]=""
laStru[218,8]=""
laStru[218,9]=""
laStru[218,10]=""
laStru[218,11]=""
laStru[218,12]=""
laStru[218,13]=""
laStru[218,14]=""
laStru[218,15]=""
laStru[218,16]=""
laStru[218,17]=0
laStru[218,18]=0
Create Table (FORCEPATH("tablename_here.dbf", this.cLocation)) name "tablename_here" from array laStru
	Create Trigger On field143  for insert as _RiHandl("Ins_tablename_here")
	Create Trigger On field87  for update as _RiHandl("Upd_tablename_here")
 Alter Table tablename_here Add Primary Key the_PK Tag PK
Index on field123 Tag onetwo collate 'MACHINE'

And then it goes on with the remaining dozen indexes, and so on for each table. Then one long procedure to set relations, one to set RI code, one with stored procedures (prety much like Ken's .krt files but base64 encoded, and cut into manageable pieces so they aren't separate files to get lost in transport). It looked ugly as hell, it was execute-only code, but it worked.