Michael If you want to keep the database on a private network sans internet that can be done.
Likely a solution that seems to work well is SQLite backend with a small server/web page doing the front end. Until you get to millions of transactions this usually is the easiest database to learn first before going to MySQL/postgreSQL/ for the back end Ruby on Rails containers can help in keeping users happy on the front end. Allowing for point and click functionality. However likely the simplest thing to do is continue with the single workstation disconnected from the internet and epoxy the network ports. And lock down the user profiles, remove unnecessary applications, institute paper log of access for printing mailing labels only! Power the system down and lock it up Update the database system mailing list with a floppy disk, cd-rom, DVD Massage the data using another workstation also disconnected from the internet Attempt to run new and old system in parallel until you can backup verify from bare metal that the backup and the new system works perfectly for your needs. For most conversions from Legacy XP type proprietary database systems, a LA Access, this will work if you want to spend the time and effort to convert to a new system with SqlLite/postgreSQL Your mileage may vary Good Luck in your mission Cheers Justin -- ------------------------------------- Justin W Elam E-mail :> [email protected] ### -- -- You received this message because you are subscribed to the Google Groups "NLUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nlug-talk?hl=en --- You received this message because you are subscribed to the Google Groups "NLUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
