Take fields from module to use them in other modules

I cant create more fields, 250 is the limit. I need to find a way to include more fields in my module.

I know there is a way to include complete modules in other modules but i dont know how.

Help please!!!

Trying to put many fields in a module is surely a problem with bad database design. You should be dividing that information by type and making related modules.

If you want to share what your information is about, and what kinds of things you’re including in those 250 fields, I can try helping you design your database a bit better.

Where did you read that 250 is the limit?

Are you getting any error messages on screen? If so please post.

Are you getting any error messages in the logs? If so please post.

I’m not sure but, maybe, reading this can be of help:

I agree in full with @pgr

i have this inthe log

Fri Feb 22 14:40:29 2019 [26150][ed6a278f-ba3b-db3a-18fc-5c50b9f8c1de][FATAL] Mysqli_query failed.
Fri Feb 22 14:40:29 2019 [26150][ed6a278f-ba3b-db3a-18fc-5c50b9f8c1de][FATAL] Cannot create column Query Failed: ALTER TABLE bitag_bitacoraagronomica_cstm add COLUMN jonh_c varchar(255) NULL : MySQL error 1118: Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. You have to change some columns to TEXT or BLOBs
Fri Feb 22 14:40:29 2019 [26150][ed6a278f-ba3b-db3a-18fc-5c50b9f8c1de][FATAL] Exception handling in /mnt/gcap-latam-vol/SuiteCRM/include/MVC/Controller/SugarController.php:402
Fri Feb 22 14:40:29 2019 [26150][ed6a278f-ba3b-db3a-18fc-5c50b9f8c1de][FATAL] Exception in Controller: Falla de base de datos. Consulte suitecrm.log para obtener más información.

looking in the MySQL, the table where the fields are created

| b2_02a_1_otro_c | varchar(255) | YES | | NULL | |
| b2_07a_1_otro_c | varchar(255) | YES | | NULL | |
| b2_12a_1_otro_indique_c | varchar(255) | YES | | NULL | |
| b2_17a_1_otra_especifique_c | varchar(255) | YES | | NULL | |
249 rows in set (0.00 sec)

The error refers exactly to the explanation I linked in my previous post:

(read it)

You can’t do anything because this is a limitation of MySql

The only option that you have is to rethink your fields structure as suggested by @pgr