Hmmm not familiar @cheezsteak. Sounds like a custom error. Did you check out the master list on MSDN?
@Mat'sMug
> Recursive descent compilers strongly reward simple, clean language design, in that it is a lot easier to write a recursive-descent parser for a simple, clean language than for a convoluted, messy one.
So, what's a good approach to parsing a convoluted and messy language then? Lol
That worked. For some reason when I selected the whole column, it said number. But when I selected the individual cells (all the cells except the header) then I got the option to convert it
Single quotes are problematic in our systems. Some of our systems do escape, and some don't (like SNAP, it throws an error instead if you use single quotes in data fields)
You could save your workbook as an add-in (.xlam) - an add-in loads with Excel, and runs at application level. You can reference an add-in in a macro-enabled workbook, and use the functions and objects it exposes:
The flipside is that anyone using workbooks that reference an add-in, will requi...
First things first - if you're going to need to maintain T-SQL, it's best to make it easy to maintain first: start with proper indentation and vertical spacing:
SELECT
product_table.ProductCode as product_code
,SUM(grouped_store_orders_table.po_qty*product_pack_sizes.pack_size_qty) AS ...
seriously.. millions of rows in mysql... is suicidal IMO
> [Flat File Source [70]] Error: Data conversion failed. The data conversion for column "OrderBook" returned status value 2 and status text "The value could not be converted because of a potential loss of data.".
Examples below work with empty columns, but not with column B. For some reasons adjacent non-empty columns are also selected with either example.
Range("B1:B1000").Select
Columns("B").Select
You could save your workbook as an add-in (.xlam) - an add-in loads with Excel, and runs at application level. You can reference an add-in in a macro-enabled workbook, and use the functions and objects it exposes:
The flipside is that anyone using workbooks that reference an add-in, will requi...
Examples below work with empty columns, but not with column B. For some reasons adjacent non-empty columns are also selected with either example.
Range("B1:B1000").Select
Columns("B").Select
VBA Rubberducking
VBA Rubberducking