About incorrect access violation and too condition consecutive exceptions, Solution

Today, there is heavy rain outside. I don't know if it will cause a flood. When it was raining outside, my sweat in my chair seemed to rain heavily.

After completing the Software Update module yesterday, the customer needsProgramMake it into MDI ). Let's do it. The program is finished, F9. Fortunately, there is no problem (my heart is beautiful). When the problem is closed, "... too category consecutive categories... ", I almost fell down. Did I change a program without a bug to a bug? It seems that there are no problems,CodeThe same is true. No way. Let's take a look. Yo, I found a global tlist which was not free when the assignment was repeated. Now that the problem is found, let's get free. After running it, a new problem occurs, that is, "access violation ". I am finished, so there is no way.

The last trick is to restore the bacupk file (often backup projects are a good habit) and check whether there is a problem. I don't know about a shipment, "... too category consecutive categories... ", it even appeared. It seems that there are bugs in it, and there is no way to rummaging through the cabinets to find such information. The time of one day is just a little bit lost.Article"If the string type of Delphi is used in the DLL, you need to add sharemem to both the DLL and the main program ". I know how to add sharemem to the DLL project, but what should I add in the main program? I don't understand this. Why didn't I solve this problem before? Add and add it. As a result, there is no problem at all. Alas, I really don't understand. Finally, when creating a DLL project, Delphi gave me a comment.

Important Note about dll Memory Management: sharemem must be
First unit in your library's uses clause and yourProject's (select
Project-View Source)Uses clause if your DLL exports any procedures or
Functions that pass strings as parameters or function results. This
Applies to all strings passed to and from your DLL -- even those that
Are nested in records and classes. sharemem is the interface unit
The borlndmm. dll Shared Memory Manager, which must be deployed along
With your DLL. To avoid using borlndmm. dll, pass string Information
Using pchar or parameter string parameters.

Have you seen the project? Well, this is where the problem is. Don't worry about the number of bugs in D7. Most of the time, D7 has given us a prompt. Hope that friends with such problems can solve their urgent needs.