I am not a computer-literate person. What does CVS stand for?

estaj

I am not a computer-literate person. What does CVS stand for?

volvogirl

Did you mean CSV? That is Comma Separated Values. You can open it in Excel, etc.

https://en.wikipedia.org/wiki/Comma-separated_values#:~:text=A%20comma%2Dseparated%20values%20(CSV,name%20for%20this%20file%20format.

Or CVS is a drug store.

Ps56k2

CSV- looks like this - Comma Separated Values…

here is a sample download from a savings account -

Date, Time, Amount, Type, Description
2023-07-10,23:45:54,202.36,Deposit,Interest Paid
2023-06-10,23:29:26,200.43,Deposit,Interest Paid
2023-05-10,23:44:40,188.74,Deposit,Interest Paid

Rocket J Squirrel

CSV does not look like what @Ps56k2 originally posted (tabular format). It is plain text with data separated by commas. In its native state, one of those lines would look like this:

2023-07-10,23:45:54,202.36,Deposit,Interest Paid

Sometimes each field is enclosed in double quotes just in case a verbatim comma might appear in a field.

Ps56k2

I originally posted exactly the normal compressed CSV but the forum website put it into a tabular format … so I added some text to just leave it as is …

skeleton567

The CSV format has been around for many years, and is probably the simplest, most sharable formats between software packages. I have had problems with commas embedded in data items such as large numeric quantities, comment fields, etc and have needed to write SQL procedures to 'clean' my data inside a database, but once removed, all is OK. In some cases I have had to go back to my original data in Quicken and remove commas before i export to CSV.

skeleton567

Volvogirl, I notice your tag about staying on QW2013. I 100% agree. I'm staying on QW2014 Premier. I don't ever fight with download problems, just enter all my data manually. I do use the EXPORT function to move data from Quicken to my relational database system. My current Quicken file contains a total of 54 active and historic accounts with data up to 80 years old.

What I would like to see the Quicken folks do is actually create a thorough VALIDATION application we could use before even attempting the import. We did it this way when I started developing computer applications, especially for the banking industry, back in 1969. And our policy was that we EXPLAINED EXACTLY WHAT THE PROBLEM WAS when it was kicked back to the folks creating the data. They had to clean up the data and re-submit it to the computer systems.

And besides being available to US, the application could even be used BY THE DATA-PROVIDING INSTITUTIONS to validte their submissions before they are sent out.

Duh….