|
Jeff, corruption in Access databases for image and memo fields is a topic for discussion; some tell they experience it regularly, some (like me) experience it never or seldom. In fact, we have had the issue at one single client only. But when some have reported about it, I felt it should be mentioned.
The reason for the possible issue is that these data objects are stored in a different matter than other fields due to their potentially large size. If a record has such a field, only a pointer is stored with the record while the actual data are saved at separate "pages" which can be located anywhere in the database file. Creating such a record represents no problem - however, issues may arise when multiple users start editing such a record. The result can be that the pointer doesn't get updated correctly, and the record looses track of its memo/image/blob field. Quite often, text stored in memo fields are nothing special, just more than the 255 chars that a text field can hold. If so, and if corruption is experienced, the method described is quite simple to implement.
Satcomer, why Access is not available for the Mac is a very good question. It has been requested by many, indeed when MS Office is available. An answer has never been given. In fact, the JET database which Access uses is not even available for 64 bit native Windows (must run in a 32 bit subsystem) and will not be, so one might wonder what database MS will use for Office should it arrive in a 64 bit version. I doubt they will push everyone to install a SQL Server 2008 Express 64 bit, and the single-user SQL Server 2008 Compact Edition (much like JET but SQL Server compatible) won't fit the bill. Time will show.
That said, today it is nearly a non-issue to bring a Windows app to a Mac user. We use the Terminal Client (Apple download) and a terminal server like that from Microsoft or - more often - ThinSoft WinConnect XP which is cheaper, much easier to set up, and much easier to administrate licenses for. Highly recommended.
As you can figure out, this has the advantage that we can mix Mac users and Windows users with a very predictable result. Windows users and the terminal server are connected on a separate network, and the Mac users need only to gain access to the terminal server. The Mac admin relax because no traffic is brought into his net, and the Windows users live quietly with their own network printer and servers.
Again, I'm not saying that a totally integrated network can't be established, of course it can as you and Jeff know, but this is a simple and pragmatic solution with a success rate of 100%. If no one else then the CFO loves such.
It seems as you regard age as a qualification - thank you - so let me just put, that my former company did networking with Luxor workstations before the IBM PC was brought to market, and I have been with pc networking since Novell NetWare version 2.0 (running on ArcNet which you may recall).
Though somewhat off topic (neither Access nor JET nor the article originally referred to is dependant on AD) I'll certainly make a note on your link to Macs on AD, though that's the kind of work we normally leave to our Mac friends.
Fryke, the super moderator, sorry to disturb you, that was not my intention, but the original questioneer as well as readers who later might look up this thread - I guess you regard your forum as a knowledge base as well - deserved a little more in favour of his modest and polite question. He could have left a note by the article, then I would have been notified right away - sorry to have caught attention to the thread at a later moment.
/gustav
 |