I don't think you are going to be able to completely 'protect' all of those items. If it is that important, I know companies like Oracle (I don't know about SAP's products) have fairly obscure tables with obscure column names, etc. You may consider that option: Have data structures that only your company can understand. I would assume that it makes for a maintenance nightmare and could potentially cost more in the long run, but if your business model calls for a highly proprietary system, that's a tactic that highly proprietary systems will sometimes take.
Cheers Ray --- Girish Mohata <[EMAIL PROTECTED]> wrote: > Hi All, > I am currently desinging a commercial application using SAPDB as the database > and Visual Basic program as the GUI. The application will be mostly data driven > hence the data structure (tables, keys, procedures, etc) are a very important > part of the complete system. The database will have to be installed at customer > offices. > > My question is: How can i restrict other people (including other vendors/ > clinets, etc) to see what the data model looks like. I know i can do it by > simply protecting the password for the user under which the tables,etc will be > created, but i want to give my customers liberty to be able to change the system > password or even provide them with the password to be able to do backups's etc.. > > Any help would be much appreciated. > Regards, > Girish > > _______________________________________________ > sapdb.general mailing list > [EMAIL PROTECTED] > http://listserv.sap.com/mailman/listinfo/sapdb.general __________________________________________________ Do you Yahoo!? Yahoo! Shopping - Send Flowers for Valentine's Day http://shopping.yahoo.com _______________________________________________ sapdb.general mailing list [EMAIL PROTECTED] http://listserv.sap.com/mailman/listinfo/sapdb.general
