Susan Harkins
ssharkins at gmail.com
Tue Nov 27 07:00:30 CST 2007
I'll check that -- on my system, anything's possible at this point, although I didn't do it myself. :) That's a good tip in itself. :) Susan H. > Also make sure that the setting in general tab of options dialog box in > VBA window has not inadvertently reverted to "Break on all errors" > > A.D.Tejpal > ------------ > > ----- Original Message ----- > From: Susan Harkins > To: Access Developers discussion and problem solving > Sent: Tuesday, November 27, 2007 00:45 > Subject: Re: [AccessD] ADO > > > Charlotte, I'm just trying to use that technique we wrote about years > ago -- > using the query field Description property. I'm using it differently, but > like I said -- works fine until I run into a query field that doesn't > have a > Description property setting. > > However, I'm going to try it on another system. This one really does > behave > badly anymore. I can't trust that what's happening isn't just something > that's broke, especially since A.D. said Resume Next worked fine for him. > > Susan H. > > > > The simple answer is NO. The query/view doesn't expose field > > properties, those are in the table. Why would you try to use a query > > for this? > > > > Charlotte Foust > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com