The short answer is that you can't because a ModuleId is not assigned until an installed module is added to a page of the site. In some cases I have pre-populated tables with installation wide (not module specific) values signified by either a bit data  "Global" column or a -1 in the table's ModuleId column.

In most cases, however, module specific data should be added to table(s) when a module is accessed for the first time after being placed on a page. If the module makes use of one or more ModuleSettings, your code can recognize that it is being accessed for the first time if the module's Settings object is empty or you can define a specific Setting key/value to signifiy that the module's data has been previously initialized.

Another approach for "global" data is to key that to either the DesktopModuleId or ModuleDefinitionId as appropriate. These can be obtained in your implementation of the IUpgradable interface in your business controller class. The implementation's UpgradeModule method will be called once for each SQL dataprovider file version greater than the currently installed version which makes it the best place for version specific code to be run during installation.

---

Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner