Can importing procedures between APPS trash the filters?

uncategorized
1

Hi,

Busy with a cleanup and re-organise exercise of my NTWS multi-dll solution.
After my first “import procedure from another app” it seemed to trash all my filters.
The copied procedure was not the problem, however many other procedures were affected.

Had to restored my app from backup.

Is this a known issue? or was I just unlucky in this exercise with the wrong sequence or something.

thanks

Johan

2

If you export to a TXA, can you search for the filter in the TXA?

3

Hi Richard,

Not sure, dumped the app and restored a backup.
Was just wondering before I attempt similar again or to know what to avoid.

thanks

Johan

4

It shouldnt but thats why I said did you look in the TXA, you should see the filters in the TXA.

The only exception is if the template is storing data outside of the AppGen .app file, which is possible.

The template commands #Create, #Open, #Read, #Close, and #Run & #RunDll make it possible to store data outside of the AppGen and likewise import data (excluding #Run) into the AppGen .app file.

5

I have found problems importing from an APP, not the problem you mention. One is it deletes all the Empty Modules and Renumbers.

What I always do is use a TXA in the middle.

  1. Open the “Source” App and do a “Selective Export” of just the Procedure(s) you want
  2. In the “Destination” App do an Import TXA and select the TXA you made in step 1

This also allows you to View and Edit the TXA before import e.g. you can change a procedure or file name. It also easily allows multiple tries as you fix a problem in the TXA then retry import.

Curious if use a TXA do you have the same problems?

6

The problem is in the use of ' (or more likely '') in filters.
Some people have taken to replacing that with <39>.
One of these approaches can be an issue when importing a TXA.

As Richard says, it’s best to inspect the TXA to see what it looks like there.

(Some Clarion versions are also better at it than others.)

7

Hi,

Thank you for all the feedback and ideas.
The app that had the problem was not the recipient app, but the source app.
I did not notice that the source app was already opne in the IDE, when I tried the import from the target APP, and had to close it first and then do the import.
Not sure if that had anything to do with it.

But will def try the selected TXA export and import, seems like a good safe option.
And yes, it did look like the quote problem that Bruce was referring to.

thanks

Johan