Welcome to NexusFi: the best trading community on the planet, with over 150,000 members Sign Up Now for Free
Genuine reviews from real traders, not fake reviews from stealth vendors
Quality education from leading professional traders
We are a friendly, helpful, and positive community
We do not tolerate rude behavior, trolling, or vendors advertising in posts
We are here to help, just let us know what you need
You'll need to register in order to view the content of the threads and start contributing to our community. It's free for basic access, or support us by becoming an Elite Member -- see if you qualify for a discount below.
-- Big Mike, Site Administrator
(If you already have an account, login at the top of the page)
Because you have also selected the protected cells..
Green heading indicates (in most cases) unprotected cells underneath.
Easiest is to delete the data column by column (except heading).
If you get an error message then, just move on to the next column....
ya thats really odd, i cant delete the selection as a whole(as shown in the picture), but i can delete all the columns selected in the picture one by one..
for some reason the screen grab didnt get the highlighted areas in the pic... i had all of the green columns in the picture highlighted..
also after clearing out the journal one by one, i went to the overview tab to put in my starting balance and this is what i got:
not sure if expected or not.. i know the 'Div/0' errors are supposed to be there but not the VB error..
dont believe anything you hear and only half of what you see
1.Yepp that is expected as there are hidden columns performing calcs....
2.Well I'm not exactly a VB guru, so that could be due to my buggy code, just click end (or debug if you happen to be a guru), I'll look into that in about 12 hours...
ok cool, and thanks for you help today vvhg! im not using like half of whats in this journal so i dont know if thats whats causing this error as well, but im getting this every so often(like not while im doing things in the journal, just randomly)..
here are the only utilities that i am interested in for my records:
dont believe anything you hear and only half of what you see
At this point the whole excel crashes due to some illegal operation (I suspect the recalc of the axis in the VB code).
Could be excel bug, but I had the chance to try it only on my Mac. I will try it on Win7 as well.
@madLyfe
Yes, the errors are likely to be caused by that, I will improve on that....
@petrmac
Sorry for crashing your excel. On my end it doesn't, but I'll try to improve the VB code. Would be interesting to see what happens on Win7. Runtime errors mostly occur with the y axis maximum, perhaps there is a way to only set the min and let excel do the max.