Nicholson, Karen
cyx5 at cdc.gov
Thu Nov 4 10:05:10 CST 2004
I have not had a problem, and the psycho that created this SQL backend used spaces, # signs, ? Marks, \ backslashes and asterisks in the field names. I have had to bracket all references to the field names and will get around to changing them. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of William Thompson Sent: Thursday, November 04, 2004 10:49 AM To: 'Access Developers discussion and problem solving' Subject: RE: [AccessD] Access FE Field Names with Spaces - in SQL Server BE Has it been anyone's experience either in Code, Form, Class or Procedure where field names with spaces in a SQL Server backend caused a breakage, with no work-around? My primary concern is with unbound forms and passing openargs to a popup form. Assuming no view is used to translate or alter the field name? I assume that all my field references will have to be altered to "[" & fieldname & "]" - even the fields that already have bracketed table definitions, like [Field With Spaces] in SQL Server. Bill Thompson -- _______________________________________________ AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com