Gustav Brock
gustav at cactus.dk
Tue Dec 9 16:38:18 CST 2008
Hi Drew Well, if it ain't the hardware, the software, the network nor the ldb file, you'll have to reboot the user or, eventually, drop and recreate him. Very effective, so they say. Cures a lot of related issues as well. /gustav >>> DWUTKA at marlow.com 09-12-2008 23:00 >>> Nope, in fact, I setup BOTH of his machines, his laptop a few months ago, and his desktop about 2 years ago. Not that I'm perfect, but I know I didn't set it up for anything unusual. Drew -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Heenan, Lambert Sent: Tuesday, December 09, 2008 1:13 PM To: 'Access Developers discussion and problem solving' Subject: Re: [AccessD] VERY strange LDB issue Any chance that the report writer guy has his machines set up for a non-European region? Lambert -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Drew Wutka Sent: Tuesday, December 09, 2008 12:09 PM To: Access Developers discussion and problem solving Subject: [AccessD] VERY strange LDB issue Ok folks, here's a doozy for ya'll. Our IT report writer is having some issues with a few .mdbs. In troubleshooting the issue, we have discovered that whenever he is the first person in a database, the .ldb file comes out with gobbly gook. If someone else is in the database already, the .ldb file will be fine, and his machine and access user name will be put at the end like it should be. Now, this happens from two different machines that he is logged into (his desktop and laptop) and over EITHER the wired or wireless connection. Here is an example of what it will show: ****P*************n************* That is the contents of an .ldb file that he is the first one into the .mdb for. Any ideas? Drew