Gosh, it's been like 15 years since I last posted here... I was the insane person who wrote his own EMR using the complete MS Office platform- MS Access, MS Word, MS Outlook, MS Excel. I use MS Excel for electronic billing (ie Access-> daily generated Excel text based spreadsheet-> Office Ally). I used to post a lot in the EMRUpdate site before it became stale (I'm being kind). I really liked AC and eMDs, and I was unfortunately hated by NextGen.
Why is your SQL backend having such a difficult time with your medications table? I don't get it. You shouldn't have to split it into 2 tables. There must be something else slowing down the transfer of data between your backend and your frontend computers. Could it be your LAN (100 GBPS is more than enough)? Is another program interfering with AC?
I'm still using the program that I've used/programmed since 1995, using the actual free MS Access back end tables. My medications table with both active/inactive meds currently holds just under 35000 records and the retrieval is instantaneous. I've found the limit to MS Access tables to be about 50000 records (my accounts table has to be thinned every 3 years). I do have backend and frontend i7 computers with 64GB RAM each. My frontend computer uses a TB SSD drive, so my hardware really helps with the speed.
The only issue I've had in terms of slowness is when Dragon Naturally Speaking is loaded. It's a wonderful dictation program but it uses the same processor core as MS Access so things grind almost to a halt. This is one reason why I've switched to Windows dictation- not that great, but there's almost no sacrificed speed.
Just a thought...
Regards,
Al
---------------------------------------
Alberto Borges MD
alborgmd@yahoo.com
Last edited by alborg; 05/15/2023 10:19 PM.
