A blank Calc spreadsheet is really just a bunch of folders and files zipped to make a file that's given a .ods extension. For example if I unzip a calc file this is what's in it...

blank-calc-spreadsheet.ods

��� Configurations2

�   ��� accelerator

�   ��� floater

�   ��� images

�   �   ��� Bitmaps

�   ��� menubar

�   ��� popupmenu

�   ��� progressbar

�   ��� statusbar

�   ��� toolbar

�   ��� toolpanel

��� content.xml

��� manifest.rdf

��� META-INF

�   ��� manifest.xml

��� meta.xml

��� mimetype

��� settings.xml

��� styles.xml

��� Thumbnails

    ��� thumbnail.png

In theory all these files, and many more that you've created, could exist in a data base. A python program would run that opens the database and builds a calc spreadsheet .ods file to the desired specifications using a selection of components from the database.

Thus every spreadsheet created could be unique, have a serial number, have the end Users name and address embedded in it, include BASIC or Python code, and provide a specific set of features just for that User.

While PyUNO would be used to initially create the file, there is no reason why the file can't stand on its own feet after its creation and use code that's embedded into it rather than having to make a PyUNO connection.

In theory, every spreadsheet you create is unique.

I've no idea if this has market potential or not, but from that analysis I did at the time I figured it couldn't be done with the Excel/VBA/whatever combination.

cheers,

Ian.