Windows 10 Feature Update 2004 comments

[Bob Denny]

So with it set like this, it doesn't work? What is the error?

Snap1.jpg

[Jerry Yesavage]

Here is the screen shot. Turns out I have Access on another computer and it can read these (archaic) databases. I will send some information from that machine.

[Jerry Yesavage]

Hi,

Here is the database opened in Access... looks to be the 2000 format. You see the size of Data2 versus Data.... it is very very small? But the data seem to be there. I guess all I can do is move it back to the Observatory machine and see if it runs OK (keeping the old version of course).

JY

PS After copying the file back I notices that there was a Data2 there already, so I guess the compression worked despite the error messages. It is similar in size (small) to the one Access compressed and it opens in Access with the appropriate variables.

Gentlemen, I now remember why I hated Access when it was all we had.

I guess I am safe to do the switcheroo and maybe I will be good until MS fixes the software... 5 years?

[Bob Denny]

Turns out I have Access on another computer and it can read these (archaic) databases

These databases aren't as archaic as Windows itself! As I mentioned in my update on July 30th, Access and Jet are alive and VERY well. You should be able to use the Access Repair and Compress tool, then it will run just fine in Scheduler. If you notice, there are quite a few Stored Procedures in the database, as well as Referential Integrity links between tables. I use Access to maintain all of these. Access is the right tool for the job.

[Jerry Yesavage]

These databases aren't as archaic as Windows itself! As I mentioned in my update on July 30th, Access and Jet are alive and VERY well. You should be able to use the Access Repair and Compress tool, then it will run just fine in Scheduler. If you notice, there are quite a few Stored Procedures in the database, as well as Referential Integrity links between tables. I use Access to maintain all of these. Access is the right tool for the job.

Well of course it threw an error..... I restarted and there was another error in ACP regarding a pointing error and locked file... see attached .txt I am letting it run and see what happens. If I get errors will go back to the old database.

It solved the plate OK from the first image... will just let it run.... nothing is simple.

[Bob Denny]

This is becoming a set of unrelated problems. Also I'd prefer attaching a real log. But no problem...

(exposure complete and image downloaded)
**Pointing update error from PinPoint.Plate:
Cannot write to the file, it is write-locked.

This has nothing to do with the database for the scheduler. In this case, MaxIm wrote an image, Then ACP tried to use PinPoint to open and solve it, and that image file was locked. How could that happen" Do you have some sort of file sync system that could be locking the files to sync to another drive or ???

The huge error box from Scheduler looks like ACP was shut down while the scheduler is running. That will do it. There is no practical way I can make the scheduler defend itself from having ACP killed or die out from under it. There are so may places in the Scheduler that have a cooperative interdependence with ACP. The two form a modular system. ACP is required for scheduler.

A compressed database from Access, making sure it is Access 4 not 3, should work fine. I use Access as a development tool here. The databases are definitely compatible. If the compressed database is small enough, zip and attach it to a reply, or put it in a dropbox and post the link. I will look at it here. Or you could put the 1.8Gb database in a dropbox (or whatever cloud storage) and I will try to compress it here.

[Jerry Yesavage]

Bob,

I am just sending you those screens since they just showed up and it said to send. The system ran OK after these errors. I included the write lock error, but that went away also.

I had saved the database as Access 2000, maybe that is Access3. I did not find an explanatory definition. I went back and saved it as Access 2003, maybe that is Access4. Scheduler seems to read it OK.

I want to be able to do this myself and not bother you,

JY

[Jerry Yesavage]

Bob,

Things looked good last night after saving the compressed database as Access 2003. Here is a screen shot:

You can see the size of the original, then Data 3 is the 2003 compressed version then you can see how that grew with just one night's imaging.... hopefully this will last a while...

[Bob Denny]

Thanks... Access 2000 is I believe the older DB structure. I use Access 2007 here and that's the V4 structure. I'm totally focused on this issue right now. and it's nice that the new support issues have been mercifully low. I'll have an update soon. Right now I'm licking my wounds from a failed experiment that appeared promising as a workaround. It didn't work, and there went 4 days :-( Back to working on the repro scenario for MS.