Tom Bolton
tom.bolton at donnslaw.co.uk
Tue Aug 30 03:57:35 CDT 2005
Morning all We've had a problem in the past here with linking tables into an Access .mdb from a SQL Server database - when the tables are linked, Access decides on its own primary key and creates an index. So far, so good, but then seemingly at random Access is dropping the index which results in the table becoming read-only. The problem can be fixed manually, but there's no pattern to the behaviour. I cured this before using a bit of ADOX to drop and relink the tables (an extra button, but in this case the user was pretty Access-conversant), but now in a separate .mdb looking at a different SQL backend, it's happening again - to a mission-critical application. Anyone any clues? I've Googled from top to bottom for this one, and not a sausage to be found. Many TIA as always Tom Tom Bolton Systems Developer (I.T.) Donns Solicitors Tel: 0161 834 3311 Fax: 0161 834 2317 -------------- next part -------------- The contents of this message and any attachments are the property of Donns Solicitors and are intended for the confidential use of the named recipient only. They may be legally privileged and should not be communicated to, or relied upon, by any other party without our written consent. If you are not the addressee, please notify us immediately so that we can make arrangements for its return. You should not show this e-mail to any person or take copies as you may be committing a criminal or civil offence for which you may be liable. The statement and opinions expressed in this e-mail message are those of the writer, and do not necessarily represent that of Donns Solicitors. Although any files attached to this e-mail will have been checked with virus protection software prior to transmission, you should carry out your own virus check before opening any attachment. Donns Solicitors does not accept any liability for any damage or loss which may be caused by software viruses...