What does this mean and how can I fix it? This is a standard procedure I’ve run hundreds of times every year for several years. Today, it gave me this error message.
You haven’t given us much to go on. With the limited information available, I’m guessing your database used to have a field name I, but you renamed or deleted it.
What Jim is too polite to say is that it can be hard enough to debug a database with the datasheet and all the procedures and forms available to be examined, but it’s impossible with no information at all. This is probably the simplest and most self-explanatory error message that Panorama X offers, but without quoting the code of the procedure in which it occurs, at the very least, no-one is going to be able to offer much of a guess as to why it no longer works.
Also you also haven’t said which version of Panorama you are running. That seems unlikely to be relevant here, but you never know.
Might be that at that point of that run of that procedure it thought the active database was different than the one you expected, the one in which they existed just fine. Happens to me in unpredictable sites, within old multiple database procedures, more often than I wish. Sometimes the next run works fine without changes. Other times inserting a setactivedstabase
statement before the error, setting it to the db I’d expected, fixes that site.
Why it happens that time I don’t know. I presume it reflects poor coding skills when I wrote it years ago, some of it rewritten Pan6 code in early PanX years, some of it unaltered Pan6 code. I continue to learn. I know 20+ years ago I routinely wrote Window statement intending to change both the active window and active database. Now that doesn’t seem to always accomplish both. Perhaps some statements change one or the other in ways I don’t anticipate. Perhaps as PanX grew it’s become pickier, or perhaps computer actions outside of PanX caused something to change.