Viewing the logs in a web browser is painful, especially on large structures. I open the log in a text editor and look for strings like “warning” or “Error”. Notepad++ has a good search feature which will list all the occurrences in context.
HTH, Tom > On Dec 10, 2019, at 11:14, Eric Naujock <[email protected]> wrote: > > The other thing that comes to mind is what are you looking at the report > with. I know safari really does not do a good job of viewing the report. I > have found Firefox handles it better. But if there is a report of anomalies > it should be in the report somewhere. > >> On Dec 10, 2019, at 2:11 PM, Mitchell Shiller <[email protected]> wrote: >> >> Thanks Tom and Eric. Unfortunately, I deleted both the .4DIndx and .4DIndy >> files. Let them rebuild. >> Verified the structure and still get anomalies that were found. >> But none highlighted or specified. In the Log Report. >> >> Any other thoughts before I head off to tech support. >> >> Appreciated, as always. >> >> Mitch >> >>> On Dec 10, 2019, at 1:43 PM, Tom Benedict <[email protected]> wrote: >>> >>> Some years ago I adopted the habit of always deleting the .4DIndy file (the >>> structure index) when deploying .4DC files. I adopted this as a best >>> practice after a number of ‘weird behavior’ episodes during deployment. It >>> may be superstition, but the overhead for 4D to recreate the .4DIndy is >>> very low, so I continue to do it. >>> >>> As you say, rebuilding a .4DIndx can take a lot longer, especially on large >>> data files. I only do it as part of routine maintenance. >>> >>> In this case I think you should consider deleting both, Mitch, and letting >>> 4D rebuild them. >>> >>> Tom Benedict >>> >>>> On Dec 10, 2019, at 09:41, Eric Naujock via 4D_Tech <[email protected]> >>>> wrote: >>>> >>>> I have seen cases where the index files get messed up. For my small >>>> databases I just delete the index files and let 4D regenerate them. But >>>> for big databases it may take a while to rebuild them. >>>> >>>>> On Dec 9, 2019, at 5:50 PM, Mitchell Shiller via 4D_Tech >>>>> <[email protected]> wrote: >>>>> >>>>> Hi, >>>>> >>>>> Went to verify my structure today after a week of coding. I noticed no >>>>> anomalies or issue with the db but I like to make sure all is OK. >>>>> >>>>> Verification reports that anomalies are found. But when I check the log, >>>>> none are highlighted. >>>>> I ran a repair 2X. A compact. >>>>> But verification still reports anomalies. >>>>> >>>>> Looking through the structure, the Trash has been emptied and there are >>>>> no orphan methods or forms that I can see. >>>>> >>>>> Help! >>>>> Any ideas? >>>>> >>>>> Is this an issue for Tech Support. >>>>> >>>>> Thanks >>>>> >>>>> Mitch >>>>> ********************************************************************** >>>>> 4D Internet Users Group (4D iNUG) >>>>> Archive: http://lists.4d.com/archives.html >>>>> Options: https://lists.4d.com/mailman/options/4d_tech >>>>> Unsub: mailto:[email protected] >>>>> ********************************************************************** >>>> >>>> ********************************************************************** >>>> 4D Internet Users Group (4D iNUG) >>>> Archive: http://lists.4d.com/archives.html >>>> Options: https://lists.4d.com/mailman/options/4d_tech >>>> Unsub: mailto:[email protected] >>>> ********************************************************************** >>> >> > ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
