Hi Marcelo;

 I have done this type of App many times in the past. What I did was to create a PBD tailored for each customer / region / language / etc and then store each entire PBD file in a BLOB column within the DBMS. One row per unique PBD grouped by whatever you need (ie: customer). Then publish only the bare minimum (base) parts of the App (C/S or PC based apps) as a starter App EXE.

 Then at run time from the starter App - once it figured out the customer / region / language / etc requirement and has a connection to the DBMS -then performs a SelectBLOB command for each unique PBD required. Then save their binaries from the Blob variable as PBD file in the same App EXE's main folder. Once I have those PBD's on disk beside the App EXE, then use the AddToLibraryList() command to add the dynamically acquired PBD's to the App's runtime library list - thus adding the extra visual & non-visual objects tailored for that client. From that point onward, the customized runtime App continues as per normal.  Food for thought.  HTH  :-)

Regards .. Chris

Hi! Export the datawindow that contains the report as an SRD file and which you store in the database as suggested. Luego created a datastore with this code lds.Create(stringSourceCode) which works correctly. This way, find a possible solution.

thanks for the suggestion

Hi Miguel! Yes, I'm referring to reports. If you have done this, can you tell me the steps? Do you export the datawindow to an srd file? Can you create the datawindow at runtime with this code?

Hi,

I don't know exactly what you mean with "print forms", but if it's reports, you could store them in the DB using a blob field relating them to a customer.

That would help you to get rid off the pbl per customer.