View Single Post
  #16   Report Post  
Posted to microsoft.public.excel.misc,soc.genealogy.computing
Steve Hayes Steve Hayes is offline
external usenet poster
 
Posts: 18
Default Dangers of using Excel as a database

On Wed, 08 Jul 2015 09:03:19 -0400, GS wrote:

It seems that if it finds one field in a column that looks as though
it could possibly be a date, then it will treat other fields in that
column as dates too, and store them as numerals.

So even if it is formatted to *display* as text, as entered, if one
pronts it, or saves it in a a CSV style, it will print or store the
wrong value.


So for 1 *last time*...

If you *do not* use Excel's methods to import/output the data, but use
VBA standard file I/O methods OR ADODB, the data transfers *'as is'*
without being changed by Excel.

Using Excel's import methods gives Excel license to *interpret* data
type! As you're experiencing here this is not what you want to happen*!


So you have to learn VBA and create a VBA routine for keyboard entry
to get Excel to record what you actually typed? And if you don't it
changes what you typed into something else, willy nilly?


--
Steve Hayes from Tshwane, South Africa
Web: http://www.khanya.org.za/stevesig.htm
Blog: http://khanya.wordpress.com
E-mail - see web page, or parse: shayes at dunelm full stop org full stop uk