Creating a Key keeps pointing to the A drive

The client is using NF 2.00A US. I created a key for the Job Ledger Entry table on my copy of his database. No problems. I sent the FOB of the exported table to him, and he says he imported it. He’s done this before, so I believe him. A report that uses this new key that I had previously sent wouldn’t run because it said the key for the table was missing. So I walked him through creating the key. It kept giving him an error message that the A drive wasn’t ready, and then when he put a blank disk in the drive, it said there wasn’t any room on the disk. I checked the Temp setting in the options, but it wasn’t pointed to his C drive, and the Database Information pointed to the C drive as well. I’m at a loss. Any info greatly appreciated.

This error can occur any time that the user has exported or imported objects from his a:\ drive. Once done, Navision will continue to try to use the a:\ drive as it’s workspace area. Close Navision and reopen it. The should correct the problem. Another solution is to export an object to a hard drive. In fact just about anything that will go outside of Navision should redirect the problem. By the way, this can also happen when a user imports objects from a floppy. Solution: copy object file to the hard drive and then import. Bill Benefiel Manager of Information Systems Overhead Door Company billb@ohdindy.com (317) 842-7444 ext 117

What Bill says is correct. Note: This also occurs if you change the licence file from the A: then run a report the client often freezes as it tries to run from the A:. I keep a folder for fob files on the customers PC and get them to copy the file across or save it from the email to this folder then Import from there. I use a number for the name (date YYYYMMDD) this means they are always in order. 20010413.fob 20010412.fob David Cox MindSource (UK) Limited Navision Solutions Partner Email: david@mindsource.co.uk Web: www.mindsource.co.uk

Thanks all! The solution was correct. I appreciate the quick responses.