We have a 100 or so tables with the exact same schema. The number of tables changes daily.

Is there a way to 'fool' LLBL 2.5 generated code into allowing us to map a single Entity to a table and as needed change the table that it edits runtime? As the number of tables is fluid, we can't generate a project against it continuously.

Are these tables related to other tables? Because if not, you could manipulate the final query by deriving a class from DataAccessAdapter, and then overriding the OnSaveEntity, OnFetchEntity etc. methods which receive the final query.

They are stand alone tables. (Picker info basically for a large enterprise)

I think Frans solution is the best to be done in this case. For other ideas (mainly for read-only lookups), please check the following thread: http://www.llblgen.com/TinyForum/Messages.aspx?ThreadID=5528

Also please see this answer: http://www.llblgen.com/tinyforum/GotoMessage.aspx?MessageID=65659&ThreadID=8232