Sorry if I sound confusing. I am in a big mess trying to solve this.
Old machines we have both on W10 and W7/8.
New ones are only on W10 obviously.
Working perfectly = old ones on W7/8.
Working slowly = old ones on W10 and new ones on W10.
Old ones on W10 were not used for this program, that is why I noticed this problem on this devices just now... during extensive testing.
I have no experience multi-user applications but I have installed a number of XP era applications on Windows 10 computers. Some work fine, some work with limited functionality, and some won't work at all. Considering everything that has been said in this thread, I suspect that your old software can not be made to work properly with Windows 10. If this were my system, I'd replace the two new Windows 10 machines with used Window 7 or Windows 8 machines and be done with it.
JackHughs
Hi there
@Keano16
@Try3
So did I
my reading of it is that it's still related to the application.
Another thing to do (although ACCESS is hideous as a DB) is to re-organise any DB indices -- after a lot of update queries particularly some index chains on the DB can get horribly convoluted -- also re-organising and optimising the DB should help whatever DB system is being used. Use secondary indexes as well if possible -- again not sure ho well ACCESS permits decent DB optimisation. Perhaps adding another key field would help and remember pure text searches are often really horrible performance wise on a lot of DB systems.
(Back it up first in case of failure !!!!).
Cheers
jimbo
I didn't see it mentioned but would say there were changes with Microsoft Office applications with Office 2007 such as the file formats, for example the defaults had an x added to the extension to show the new ones as in .docx, .xlsx, etc. The Access files would also have changed. A lot could be riding upon which version of Microsoft Office is installed on the older computers. Another point that may be minor is Office 2010 beginning offering either the 32-bit or new 64-bit versions, can be compatibility issues. I had to give up FrontPage of 2003 when changing to the 64-bit version of Office 2010.
I think that Office version is actually irrelevant.
I do not open .mdb files.
Accounting application manages database, not Office. Office doesn't even have to be installed on the PC.
Okay. The only actual stand-alone data base program I've used was dBase 5 when I got it for my son's first computer in college and setting up his company. Other database programs came with Microsoft Office, a few versions of WordPerfect.
I will try replacement PC with windows 8... and update you accordingly
- - - Updated - - -
My problem is still not resolved.
One important thing that I tested and found our yesterday. I borrowed a PC from a friend (PC with new hardware, i5-9400 processor, and board ASROCK h310cm-hdv m2 and Windows 8.1 x64 PRO on it and here are my findings:
- I have very similar problems like in Windows 10
- Again to mention: older PC's in the office on Windows 8 are running fine
So, my only conclusion is that something of new hardware (LAN card?) is causing slowness of this application.
I did the test:
- wireless USB lan - no success
- additional PCIex LAN card (this time tpLink/realtek) - no success
I was sure Windows 10 is the only problem... but, based on this yesteday's test, it seems that problem is (also) a new hardware. There is no other explanation.
I know I am boring but I must state again: all other PC's in the network work fine (Windows 8).
I have also called programmer (application vendor). They know that the problem is present, but they don't know the reason and they don't know the solution. And they are not too interested to investigate it.
Unfortunately we still cannot change program, so I must somehow fix this situation.
And in the end - I can confirm that various accounting companies in my country using this same application have exactly the same problem on new machines. I have spoken with their network admins and IT guys. I am not the only one.
Denis, you have just highlighted the crux of the problem with older software and hardware. It has been referred to as "Planned Obsolescence" but it really is that when a product is no longer produced and also no longer sold there is no money coming in to keep things up to date, simply economics.
Quote