it adds them with names "dbo." instead of "dbo.MessageItems_Insert" and "dbo.MessageLanguages_Insert"

as shown here in the stored procedures view on the ddt:

i tried deleting the tables in the ddt and from the database and re-adding the localization deployment packages through the wizard, but he does it again

any idea ?

You probably have a good reaoson to add the Message and Localization tables into your Database, but if not, have a look at the help file under "Using Embedded XML Files", which is the recommended way, and will probably give your application a performance boost.

Cheers.

hi Ivan,

how much of a performance boost are we talking here ? there a few reasons why i'd want the localization inside the database rather than using the xml approach, however if it raises a serious slowdown (which i havent seen indications for yet) i might get my head around it and find some solutions for the problems that arise when using xml based localization with this application.

thanks !

This can depend on a number of factors, especially on whether you intend to localize labels, etc.  The more you localize, then the more of a performance boost you will gain.  It is embedded within the EXE so no trips to the server are required.  The embedded option will be 100% instantaioneous and not impact load performance.  If you are pulling from SQL Server, then you can experience a load delay as a trip to the server will be made for each request (until it has been loaded once then it is cached during the run).

So the performance boost is extremely significant and if you intend on localizing every facet of your application, you would be well advised to embed your localization files.  If you are only going to pull messages, then it will not be that big of a deal.