I am very interested on this topic.

Ramon, what did you mean for menu and form 'definitions'? Their captions or
their location?
To internationalize our software, we use multiple DLL's to load languages at
run time, and the overload (unload the current dll, load the one associated
with the current language, and refresh all labels) is not bad. But as I said
we are using a local dll, we do not connect to a remote database. We are
sort of considering storing everything in a database, and we have the same
concerns as you do.

Every feedback is greatly appreciated.

m.
 

> -----Original Message-----
> From:	RPAmog@s... [SMTP:RPAmog@s...]
> Sent:	Tuesday, February 27, 2001 4:47 PM
> To:	professional vb
> Subject:	[pro_vb] Storing controls in databases - efficient?
> 
> I would just like your professional opinion regarding the above subject.
> As
> a programmer, I've been exposed to different programming techniques, from
> procedural to object-oriented.  Way back, I used to program in Foxpro and
> our development team decided to put all of our menu definitions, form
> definitions, etc. in the dbf files for ease in coding and development.
> Unfortunately, I transferred to another company and never got to see if
> the
> system we developed was fast and efficient.  
> 
> Recently, I had a talk with a fellow who used the same technique in VB.
> He
> says the development is easier.  But is it efficient?  I mean, wouldn't
> your
> users have to connect time and time again to your database of controls
> everytime a form is loaded?  Wouldn't this cause a lot of network traffic
> if
> implemented using SQL Server, MS Access, or some other similar database?
> 
> I don't know if I should follow the same example.  Would any of you or are
> any of you using the same technique?  What do you think are the advantages
> and disadvantages?
> 
> Are there other better alternatives?  Perhaps we can all help each other
> in
> this area.  Will be waiting for your comments.  Thanks!
> 
> Ramon
>