Quote from: K-Dog on Feb 01, 2025, 03:10 PMThe database remains quirky.  I fixed some of it by hand.  I am creating a tool to manage the confusion, as doing the job manually is very error prone.  There is a lot of juggling.

In the modern world, what does a "quirky" database mean? Once upon a time when dinosaurs roamed the Earth I wrote basic DOS stuff, because it was cool. I began with Ashton Tate and dbase III programming on PCs. I migrated from there to Access 2.0 and underlying VB programming upon its introduction, and then inline programming in Access to Oracle serves, whereby I wrote SQL code (which looks just like dbase code), ran it inside of Access, to do whatever needed done with the Oracel tables, and to get around MS Access issues with file size and whatnot.

I can't recall my databases ever having decided to just....become unstable....just because. Is this a size limitation in some weird way that when violated decides to just start changing things for fun, surely the Diner can't be so large with mostly text stuff...if we were talking stored log raster rastor files I could see things getting big, but ASCII?

Code works generally until it hits some weird other limit, I get that, and I imagine the code sits on someone elses server, but are modern server rentals so shitty they can't run little websites and keep all the things pointed at the right stuff?

Isn't an instruction required somehow of some sort to begin a randomization process that can deep six all the internal connections?