[AccessD] Fascinating (but schtupid)

Stuart McLachlan stuart at lexacorp.com.pg
Mon Feb 6 14:02:09 CST 2012


SYLK is a proprietary MS data exchange format.
http://en.wikipedia.org/wiki/SYmbolic_LinK_%28SYLK%29

The only people who have to "work around it' are those who open CSV files in Excel.  I 
always set my machines up to use a good text editor as the default program for CSV files.

-- 
Stuart

On 6 Feb 2012 at 13:56, jwcolby wrote:

> Oh MAN did you read this?  If the first two characters of a CSV have 'ID' Microsoft unilaterally 
> decides it is a SLYK file?  First of all, what is a SYLK file?  And why doesn't MS fix this instead 
> of making the entire world work around this *Microsoft* problem?  Or have they?  Notice that the 
> "Applies to" does not include 2007 or 2010.
> 
> John W. Colby
> Colby Consulting
> 
> Reality is what refuses to go away
> when you do not believe in it
> 
> On 2/6/2012 10:58 AM, Mark A Matte wrote:
> >
> > Here is another 'no-no':  http://support.microsoft.com/kb/323626
> >
> >
> > Last week I exported from Access to CSV...and the recipient said the file was corrupt...With a little research it was determined you CANNOT have the first 2 letters in a CSV file be 'ID'... they can be 'id'...just not capitalized.
> >
> > Just adds to the list of gotchas lurking in MS.
> >
> > Mark A. Matte
> >
> >
> >
> >
> >
> >> Date: Sat, 4 Feb 2012 14:18:07 -0600
> >> From: garykjos at gmail.com
> >> To: accessd at databaseadvisors.com
> >> Subject: Re: [AccessD] Fascinating (but schtupid)
> >>
> >> Ya done confused it John. ;-) Name, date, time, format - those things
> >> are all bad ideas to use for names on anything aren't they? Glad you
> >> figured it out.
> >>
> >> GK
> >>
> >> On Sat, Feb 4, 2012 at 1:58 PM, jwcolby<jwcolby at colbyconsulting.com>  wrote:
> >>>> It worked just fine for a while, then suddenly didn't work.
> >>>
> >>> Likewise, it was working fine for awhile then suddenly started the uesrname
> >>> / password thing.
> >>>
> >>>
> >>> John W. Colby
> >>> Colby Consulting
> >>>
> >>> Reality is what refuses to go away
> >>> when you do not believe in it
> >>>
> >>> On 2/4/2012 2:45 PM, Tina Norris Fields wrote:
> >>>>
> >>>> Aha! Yes, I did that very same thing a few years ago. It worked just fine
> >>>> for a while, then suddenly
> >>>> didn't work. "Name" is indeed a reserved word - changed it to "FullName"
> >>>> and had no more problems.
> >>>> T
> >>>>
> >>>> Tina Norris Fields
> >>>> tinanfields at torchlake.com
> >>>> 231-322-2787
> >>>>
> >>>>
> >>>> On 2/4/2012 2:18 PM, jwcolby wrote:
> >>>>>
> >>>>> It seems the issue behind the problem is that I used "Name" as the field
> >>>>> alias back in the view in
> >>>>> SQL Server. Name is almost certainly a reserved word in Access. When I
> >>>>> changed the alias to
> >>>>> something else the problem went away.
> >>>>>
> >>>>> John W. Colby
> >>>>> Colby Consulting
> >>>>>
> >>>>> Reality is what refuses to go away
> >>>>> when you do not believe in it
> >>>>>
> >>>>> On 2/4/2012 1:14 PM, jwcolby wrote:
> >>>>>>
> >>>>>> I am working on an Access database which uses ODBC links back to tables
> >>>>>> as well as views. Everything
> >>>>>> was working fine until I created a view which appends a FirstName + ' '
> >>>>>> + LastName to create a name
> >>>>>> field, for use in a combo. I have a couple of dozen views which I link
> >>>>>> into the FE but this is the
> >>>>>> only one so far where I do this append kind of thing. I use these views
> >>>>>> to sort the data out at the
> >>>>>> sql server end and populate my drop down combos in various forms.
> >>>>>>
> >>>>>> When I bind the combo to this view and open the form, a SQL server login
> >>>>>> form opens several times.
> >>>>>> You know the one I mean, the login form which asks whether to use
> >>>>>> trusted connection or a SQL Server
> >>>>>> username / password. The view itself is fine, I can click on the view
> >>>>>> and see the data, no login
> >>>>>> form etc.
> >>>>>>
> >>>>>> If I bind the row source to the corresponding table and do the append
> >>>>>> thing inside of Access I also
> >>>>>> do not get the login form popping up.
> >>>>>>
> >>>>>> So, bind to a view without this field append happening back in SQL
> >>>>>> Server, no problem.
> >>>>>> Bind to a table and do the field append in the FE itself, no problem.
> >>>>>> Open the view with the field append happening in SQL Server, no problem.
> >>>>>> Bind to a view with this append happening back in sql server, log in box
> >>>>>> pops up, several times.
> >>>>>>
> >>>>>> Check this out, if I relink just that view, the error goes away... until
> >>>>>> I close the database and
> >>>>>> re-open it and then the error is back. Relink the view, gone, close
> >>>>>> re-open and it's back.
> >>>>>>
> >>>>>> Of course it took me awhile to figure this out.
> >>>>>>
> >>>>>> Doncha just love Access?
> >>>>>>
> >>>>>
> >>>
> >>> --
> >>> AccessD mailing list
> >>> AccessD at databaseadvisors.com
> >>> http://databaseadvisors.com/mailman/listinfo/accessd
> >>> Website: http://www.databaseadvisors.com
> >>
> >>
> >>
> >> --
> >> Gary Kjos
> >> garykjos at gmail.com
> >> --
> >> AccessD mailing list
> >> AccessD at databaseadvisors.com
> >> http://databaseadvisors.com/mailman/listinfo/accessd
> >> Website: http://www.databaseadvisors.com
> >   		 	   		
> 
> -- 
> AccessD mailing list
> AccessD at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/accessd
> Website: http://www.databaseadvisors.com
> 




More information about the AccessD mailing list