G'Day Paul,

You might try the following.

Award reports depend on data in the Lists table as well as your log. There are fields in the lists table for every value for the various Award lists in the table. The field values are generated from your QSOs in your log when you run - Awards, Update Awards Progress info.

Try running Awards, Update Awards Progress info, the will generate new data and new indexes. Then try the reports again.

You should endeavour to correct any "rejects" reported in the process.

Also, check in the root directory of C: to see that progress.xls and progress.txt are actually being created. These files will remain in C:\ even after you exit LOGic. If these files are not being created you may have a "permissions problem".

I hope the above helps.

Thank you Peter and Dennis.

I am running version 9.0.57. I renamed the existing Cards needed landscape files and put the ones you sent in the REPORT file. Same results.

I cannot locate the progress.xls or progress.txt files anywhere.

Paul W5PF

Thanks Dennis, I went to the bottom of the LOGIC 9 Update page and didn't realize there were more pages. Now I have 9.0.66 and get the same error. I ran the Cards Needed Landscape report for IOTA on Aug 8 with no problem. When I tried to run it yesterday I got the error. I have not added or changed any software but Microsoft made a "Critical update" on Aug 10th. They must have changed a setting somewhere. I am running Logic "As administrator".

Paul W5PF

I tried mine with IOTA thinking it might be a problem related to user-defined fields, and no problems.

Mauro makes a good point -- close anything generating spots to be safe. However, this does not seem to be the sort of error caused by this. I will look at the code and see if I see anything that might be a clue.

Tnx/73,

DH

G'Day Paul,

I know how you are feeling Paul. Been there, done that.

This topic will show you what to do.

...have you run Awards, Update Awards Progress info?

Have you dealt with all the exceptions reported in that process?

Have you closed the SpotLog and Telnet when you run the reports?

When errors occur, run CLEAN. This is tedious I know, but getting the Foxpro databases and indexes in LOGic back to a "known state" is important. It helps keep the errors from compounding, and makes it easier to track down the root cause.

We each have a log, and other data - each is a unique data set with complex interrelationships. It is wise to separate "operating" from "reporting". Trying to run reports while operating, or waiting for the DX, can create "complications" within the relationships within our unique set of data. Complications best avoided.

G'Day Paul,

Again, I sympathise with you Paul. Keep in mind that, copies of LOGic are probably measured in thousands. It is a big ask for anyone to be able to find all the "issues" that might arise in such a small population of users. It is up to us to provide the constructive feedback to improve the product. Those using LOGic to an advanced level are probably measured in hundreds if we are lucky.

This forum is an ideal place to share experience with LOGic.

LOGic has improved a lot over the years. But the problem is not as simple as "LOGic is getting too complex".

Lots of things change. New versions of Windows, continuous updates to Windows, updates to the Microsoft .Net run time systems. The list goes on and on.

Your PC itself changes over time - simply by using it - and of course by adding/updating various other software components as well. Many things might seem totally unrelated to LOGic, but in reality, each has its affect.

In fact, the only thing that has NOT been changing is the Microsoft Visual Foxpro run time library system used by LOGic. Microsoft stopped development at Ver 9, many years ago. That said, Visual Foxpro is still in production in thousands of commercial systems world wide.

The more one reads the forum, the more one realises that many things external to LOGic often result in problems for LOGic, but have nothing to do with the LOGic software itself.

Please let the forum know if you again experience the problems.

I think I fixed it! Update coming soon.

73,

DH