Search the Community
Showing results for tags 'mac mini'.
Found 2 results
I am going with a mac mini, maxed at 16gb, and with four cores, either the current or the new ones, which I expect to have pci ssds (which is no big deal if you'll be running your db from ram anyway), for a 50 strong company with 1-6 concurrent connections, for the time being. I ‘ll have for starters about 2-3 go clients, 5 desktop clients, and the rest will be webdirect. On average I would expect 3 people to be inputting at any time and about another 3 browsing the db. Are there any red flags that I should be aware of?
I am looking for some advice for having users remotely connect to our database for data entry only. Originally, we used IWP, but it was frustrating because we have a number of fields that use value lists with related values (the second field would be dependent on what has been selected from the previous field) and with the IWP we had to commit the record by pressing save in order for it to "refresh" and populate the next field's value list. This made data entry take too long. Currently, we have FM 11 Server on one server, and we have all of the user licenses living on a Mac Mini. Users access the Mac Mini through Share Screen/Remote Desktop and use the Open Remote feature to open the database. However, often there is a slight lag, as with any remote desktop. We use AquaConnect so that multiple users can log into the Mac Mini at once and not share the same screen. Are we complicating this too much? Is there a better way we could be allowing users to remotely connect to our database? Thanks for your help! Arbel