>>We have just converted a complete application (2 dbc's including a total of about 150 tables with about 1-2 gb of test data) to a client server system using SQL Server. We have all the remote views in the shared dbc's on the server, but as we are now changing and enhancing the system, we have decided to create the dbc's locally and the views programmatically. This will help us, we think, with the ever-changing table layouts over the next year. We have classes setup to help us do this relatively painlessly, but I'm wondering what pitfalls we are in for. Any info would be appreciated. Thanks.
>
>If your concern is dynamically changing data, then I would recommend having the dbc destroyed and created every time the app starts. Otherwise, creating views on the fly programmatically will cause your dbc to bloat.

Thanks, we are doing that. I saw a previous thread from you that didn't recommend this. Did I understand you right?