Issue with excel 2016 64 bit and excel 2013 32 bit.

So Im working in a project with vba, I have two machines, one's at home, and the other one at my job. There are these small things Im having trouble with. When I work at home, Im working with Excel 2016 64 bits, so I write down code and everything works. Once I get to my job, sometimes the code fails. At my job, I work with Excel 2013 32 bit, so this is causing me trouble because I spend more time solving these new issues I've got because of versioning than actually writing code.

All I want to know is if this is a thing. I mean this is my conclusion because of self experience, but maybe you guys can tell me that Im not crazy and this is actually a versioning issue. I've tried searching in the web for an explanation and I haven't found anything solid yet.

So, just to give you an idea...

I've got this code with 2016 64-bit:

Please Login or Register  to view this content.

Basically, tb_Interes is a textbox with a percentage value, so Im dropping the percentage and getting just the number, dividing it by 100, adding 1 and finally multiplying by tb_CantidadSiguientePagoSemanal, which has the value that I want to apply the percentage:

-> 10%
-> .1
-> 1+.1 = 1.1
->1.1 * (tb_CantidadSiguientePagoSemanal)
-> Save the value in the same textbox tb_CantidadSiguientePagoSemanal

While working with Excel 2016 64 bit, everything works and I get the value I want, but when I'm in 2013 32 bit, it fails with a type mismatch error

If it's a compatibility problem, is there any recommendation/solution that you can provide? I'm tired of rewriting code, feels like double working the same issue.

I will appreciate any answer,

Regards!!

Guess It's impossible to work with both versions, I would need to rework always if I want to use both. I'll keep 2016 64 bit

Thanks for the answers!!

I think it's just unnecessary to work in both versions, but I thought I could work in both using the same code. I will just start using use one.

Yup, doing some research, it should work on both, but I already spent a lot of time reworking and doing research, and this code works perfectly on 2016 64 bit so, as I said, I will just stop using 2013 32 bit, thanks!!!

I cant show the entire code, it's kind of huge, it's true that it could be another thing popping the error but it's not the first time this happens to me while migrating my job to version 2013 32 bit, so it gives me reasons to think about this being the root cause of the error. I have had a lot of problems using VBA's Format, Application.WorksheetFunction.Text was my last option to write down, but it worked. I'll prepare the piece of the code so you can check it, but so you can have a little bit of insight...

The issue I had, I was saving a value from a TextBox to a cell in a worksheet as Currency. Let's say 192.37. To save it, I just did a Worksheets("Sheet1").Cells(1,1) = CCur(TextBox.Value), and in cell it looked like $192.37 (I didnt use any format, just changed the data type to currency). To display that number back to another textbox, I took it from cell(1,1) and running the userform the number looked like this 19,237, or this 19,237.00. I tried everything, VBA's Format, change the number to Double and back to Currency, concatenate $ symbol, tried every format I found on internet and didnt work. It was until I found in a youtube video where they were using Application.WorksheetFunction.Text and it worked very well, I can even make calculations with the value and save it back to worksheet, I'm not saying is the most efficient way or even the right way, but after hours searching for answers, it worked for me.

As I said, I will make a small document so you can see the code and try to figure out what's happening, but that currency data type along with the text box had given me a really hard time.

Thanks everyone for the help!! Feels good to finally get answers. Hope you can see the file in a few hours.

Then what's the difference between using Application.WorksheetFunction.Text and the Text property? Aren't they the same in functionality?

Alright, I will change it then, and will let you know if there are further issues, thanks!!!!