@Simcfc73 did you have any luck with this - we're also seeing issues with Food in Focus, MDB is stored on a SAN/NAS device served by CIFS.
I have a piece of software that connects to a MS DB on a 2008 server (its called food in focus). Its locking people out when they log out and back in...or if there are 20 or so people using it. I was told it could be the MS Access connection limit which I thought was in the ODBC connectors in the control panel but cant find the limiter.. anyone know where it might be or if its something else.
Hmm.. I'm missing the point here, but where does Access come into play if you're connecting to an MS SQL database?
MS Access has a built in concurrent connection limit, just as Windows XP or Windows 7 do too for example. This is why Windows Server with x amount of CALs and MS SQL is the way forward so there should be no connection limitations.
It's not an MS SQL database, it's an access mdb file stored on a network share, on a server OS (in my case solaris based OS sharing via CIFS)
Also - it is possible to convert an MS Access database into SQL (google this), but seeing as it's a product you've purchased I'd go back to them first.
It is odd they've decided to use MS Access and not SQL Express (which is free), considering it's to be used in a school.
I don't know what's odd about it - shameful certainly but not odd. Far too much educational software is made by people who appear to have never actually used a computer before in their lives. Or at best, have what the charitable person might call "unconventional views" about how to build applications.
mac_shinobi (5th February 2013)
Can't help sorry, we only had a maximum of 15 kids and it was stil pants
Willott (5th February 2013)
How did you guys manage to get the MDB to run from a server? Just got Food in Focus 2, which is just a standard MSI (extracted from EXE) and absolutely no documentation. The only things the package changes is puts those files in; therefore it'll run from a shared drive in theory, yet more than one connection makes it fail.
To be honest, I can't remember... think I may have run install on server (or install on client, pointing to server drive). It's basically an exe with a mdb, so the whole program folder can sit on a share.
Something to try
MDB and program installed on the same os as what the clients will use ( will refer to this machine as the server even though it has a client os )
On the server pc launch and set options in ms access and in control panel ref limiting connections etc
Try from a number of clients and see if its the same ?
There are currently 1 users browsing this thread. (0 members and 1 guests)