Do not Delete a Custom Module from the file system..

[cjohnston]

If you deleted through the Module Builder a Custom Module, don't go and delete it from the file system unless you have spare time to fix it.

1) Check the tables acl_actions and delete instances of the module which is being removed, also check the related ACL tables to make sure you don't leave any orphaned records
2) in the file system search and remove instances of the module name under the "custom" directory there will be at least 4 files that will contain a string instance of th unique module name. Don't just delete the files that have teh string, look at them 1st and check to make sure there are no other custom module references
3) modify the Base64 encoded "config" table where the field category=MySettings and yank out the reference of the module being removed, don't forget to change the value a:# in the beginning to reflect the new amount of entries
4) Rebuild the database under Admin->Repair
5) Say you pulled out all instances of the module, you will see "PHP undefined index errors" if you didn't

Basically removing the physical files that reference a module created from the Studio will have you all over the application, a great task fun to do, hard to complete. My words would be don't remove a module's files even though it has been deleted in the Module Builder because all through out the SugarCRM application it is still referenced and ruminates are everywhere....

unless you know what you are doing and can solve the puzzle here are the places to look

Under /custom directory!
Under /module directory???
user_preferences table under the category global
acl tables and related acl table instances
config table under category MySettings