Too Many SegDef - Data DLL - Proper ways to clear this up?

I’ve read on here and in other places ways to deal with this. I’m going through and removing unused table definitions. I did the same with templates.

I suppose if push comes to shove, I can create 2 or more data.dlls and create application groups, and use JSON and NetTalk-based services to pass data and trigger processing. I already have 6 services that perform repetitive functions, allowing me to remove bottlenecks from the desktop and NetTalk server apps. Still had one dictionary.

This can help;

Also I recommend
Application Menu,
Repopulate Module Option
1 procedure per module.

If this is a NetTalk Web Server app, then there are other things to do as well.

It’s a Data.DLL. Checking “Generate the declarations in Modules” gave me 4313 unresolved references. Grr…

good, you’re making progress. What were the errors?

We have more than one data.dll. In each data.dll:
“Generate all file declarations” - OFF
“Export all file declarations” - ON
If you do like that - each data.dll will export only file declarations for files that you use in that dll.
So you need to create one “dummy procedure” and on that procedure add per example half of the files from your dictionary.
Second data.dll (data2.dll) is very similiar as first → just add the second half of files from your dct in dummy procedure… (make sure that you don’t put the same file(s) in both data.dlls… if you do that you will get a lot of errors…)..
No need to change anything else… (if you in data.dll add module data2.dll I think there is no need to change anything alse, just recompile all…).

1 Like

I’m back at it and will give it a try. Thanks