worddiva
nancy.lytle at gmail.com
Fri Feb 4 15:22:34 CST 2005
Thanks, looks like a good article, and Arthur Fuller knows his stuff. I guess maybe I need to spend a fair amount on time on starting to learn XML and it uses. I just see problems in the future and I want to avoid if possible. Thanks, Nancy On Fri, 4 Feb 2005 13:15:02 -0800, Francisco Tapia <fhtapia at gmail.com> wrote: > Nancy this topic is right "on-topic" what your boss is describing is a > specific attribute to your .exe application. (re: the settings > filename). > > This is a good article on reading xml data right out of a sql server > ... the author (Arthur) also will muse over the threads on this > list... > > http://artfulramblings.blogspot.com/2004/10/reading-xml-data-from-sql-server.html > > > On Fri, 4 Feb 2005 12:57:47 -0800, Charlotte Foust > <cfoust at infostatsystems.com> wrote: > > An XML file is a text file and you can read it with any text editor. It > > has nothing whatsoever to do with any XML "software" unless you've > > written software to look for that file name. If the application > > software is in .Net, it may be using typed datasets based on a file > > named Settings.xml and/or it may contain a class to manipulate that xml > > file. > > > > We import and export xml files with different names and we store > > settings in xml files with specific names. We also use xml files to > > store lookup values that are not part of the back end data. None of > > them is named Settings.xml but we do have to program for specific xml > > file names. > > > > Charlotte Foust > > > > > > -----Original Message----- > > From: worddiva [mailto:nancy.lytle at gmail.com] > > Sent: Friday, February 04, 2005 12:49 PM > > To: dba-sqlserver at databaseadvisors.com > > Subject: [dba-SQLServer] XML setting files > > > > I know this is a little off topic but we do use SQL Server with XML and > > I know next to nothing about XML, but I have been tasked with going into > > some settings files and adding the application name to the connection > > string, and replacing the in line SQL with a stored procedure. All of > > the files are named 'settings.xml' no matter what they are used for or > > in, it is always settings. I suggested we might want to change the file > > name to something more descriptive than settings, but my boss says that > > the file must be named 'settings.xml'. Is that true? Or is it that if > > we rename the file, we must also rename in the application .exe? My > > supervisor stated > > "The settings file is use as input into the XML process, it works kind > > like the .ini file. However the XML software looks for a file name > > settings.xml" Already I have run across a situation in SourceSafe where > > a settings file was listed under the wrong process, which is what I > > think we should be trying to prevent. > > > > Thanks in advance, > > Nancy > > _______________________________________________ > > dba-SQLServer mailing list > > dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > > _______________________________________________ > > dba-SQLServer mailing list > > dba-SQLServer at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > > http://www.databaseadvisors.com > > > > > > -- > -Francisco > http://pcthis.blogspot.com | PC news with out the jargon! > _______________________________________________ > dba-SQLServer mailing list > dba-SQLServer at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/dba-sqlserver > http://www.databaseadvisors.com > >