Arthur Fuller
fuller.artful at gmail.com
Sun Sep 30 09:18:29 CDT 2007
Yes, you need to be concerned. You might use a tool such as Rick Fisher's Find and Replace to find and replace all such column names with more acceptable names (such as Event2 and Feb95). Do this on a backed-up copy of your BE. Rick's program is excellent at finding all occurrences of target strings -- it looks everywhere: in queries and tables and code strings etc. hth, Arthur On 9/30/07, pcs at azizaz.com <pcs at azizaz.com> wrote: > > Using the SQL Server migration assistant for Access I've > migrated the BE Db OK. > I have a warning message for a number of field names that > have this in common: they all start with a digit, > for example 2ndEvent; 95Feb; etc. > > The message reads: > SQL Server Migration Assistant for Access Warning message: > Identifier name might cause problems > Column '95Feb' has a name that might cause problems for the > Access application to function correctly against SQL Server. > > Do I need to be concerned enough to change to field names? > And why? > > Regards > Borge > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > >