Double frondend to backend links following tabledef

[GraeagleBill]

I've attached a text file containing a sub code that creates a new table and adds the new fields. The code runs fine, but somehow I managed to create 2 links from the frontend to the backend. I.e., tbSermons and tbSermons1 I don't see where the second link came from, unless the tabledef functionality does the first one automatically?

I'd post the code inline here, but I don't know how to use the code tags?

Thanks,


Bill

[June7]

To use the code tags button on the Advanced Editor just click then copy/paste your code between the tags. You can also just type the tags.

Not understanding how this code works. What is IPDatabase? It is not a declared variable within the procedure. Is this code in the frontend?

Why do you need to programmatically create table as opposed to just opening the backend and creating table(s)?

[GraeagleBill]

Hi June,
The code is attending to DB updates in the field corresponding to version enhancements in the app.
IPDatabase is an installation variable that "tells" the frontend where the backend DB is located.
The posted code is one sub amongst several in a general module. I just thought it was enough to give a clue as to why two links were created where I only explicitly issued one.
Bill

[GraeagleBill]

RATS! A cockpit error. During the course of some debug, I ran the code that created and linked the tbSermons table. While the backend indeed did not already have the table the frontend still had the link from a previous run. With that, the link action produced a second link, tbSermons1. I have error code, but it didn't get called when the link was done with the same name as an existing.
Sorry I wasted your time,
Bill