Excel 64 Bits

[Tea Rochlitz]

Copy the example data in the following table, and paste it in cell A1 of a new Excel worksheet. For formulas to show results, select them, press F2, and then press Enter. If you need to, you can adjust the column widths to see all the data.

The binary representation of 13 is 1101, and the binary representation of 25 is 11001. Their bits match at the rightmost position and at the position fourth from the right. This is returned as (2^0)+ (2^3), or 9.

SASHELP.CLASS is a SAS7BDAT file. Most SAS data files have the SAS7BDAT extension on Windows and Unix. The key to specifying the correct LIBRARY name instead of SASHELP is to know where your data are located. So let me ask you this, in the code I posted, there were 2 file specifications that you had to provide:

You said in your post that " the program does not read the file location when I use it to replace the sashelp.class file" -- this implies to me that you are using either the wrong library or dataset name for the DATA= option in the code from my #2 example (shown in pink in the code above). Or, you do not correctly know how to specify a LIBNAME statement. For example, let's say that you have a sas dataset called "ORDERS.SAS7BDAT" on your shared drive (the Q drive) in a folder called Q:\allmydata\accounting\orders.sas7bdat. In order to specify a 2 level name correctly, you first need a LIBNAME statement to point to the Q: drive location:

Note how the library reference name of mydata (which you can think of as a "nickname" or "alias", but which SAS calls a "libref") is the high-level part of the 2 level name mydata.orders in the DATA=option in the code.

On the other hand, if your SAS data is a temporary file and is "living" in the WORK library, then you should be able to refer to it with either a 1 level name DATA=ORDERS or a 2-level name DATA=WORK.ORDERS. It really depends on whether you are referencing a permanent SAS dataset or a temporary one. Without seeing your EXACT code and the EXACT error message, it is nearly impossible to comment on how you should fix the issue you have. You might consider opening a track with Tech Support on this.

This may be a question for Tech Support. I am not sure that the Export Wizard will work in the scenario you describe. When I have 64 bit SAS and 32 bit Excel, any of these code methods works for me (assuming I do have the PC File Server installed). If you do not have the PC File Server installed then I am not sure that choice in the Export Wizard will work.

If that doesn't work, and as your using Excel it has a 50-50 likelihood. Try proc reporting the data to tagsets.excelxp. As that is a tagset and creates markedup text document it should not matter what bit the Excel version is:

Hello everyone,

My name is Dion and I work for an enterprise as an IT Systems Analyst. I have a user that uses SAP IBP excel add-in 64 bit and she experiences Excel crashing, Excel freezing, her laptop freezing and in some cases random shutdowns. My team and I have tried the following to improve performance.

- Teaching user how to open excel in it's own instance/session

- Adjusting virtual memory to set aside memory space for applications

- Disabling and uninstalling unused add-ins to improve performance

- Running SFC /Scannow and DISM /Online /Cleanup-Image /RestoreHealth

- Upgrading user to 64 bit office

- Reinstalling Office 64 bit and SAP IBP 64 bit

- Upgrading user's laptop to a developer laptop model with 32GB of physical memory

- Changing settings in excel to dumb cache files every 5 days to eliminate the possibility of corrupt files.

- Rebuilding her user profile

- Reimaging her developer laptop.

No change. User still experiences the problems above. It may help to know that she works SAP IBP excel add-in to the bone. She claims that she never had issues on her old Dell Laptop with 16GB physical memory. Other users in our enterprise use SAP IBP too but don't run into these issues. We have many IT Service teams in our enterprise and our SAP IBP rep believes it's user error.

I don't know how I can help her at this point, so I reaching out to this community for any leads and answers. Any suggestions or advise is welcome.

Thank you

Thank you for visiting SAP Community to get answers to your questions. Since you're asking a question here for the first time, I recommend that you familiarize yourself with -and-answers, as it provides tips for preparing questions that draw responses from our members.

We recently upgraded a client using AP and GL only to version 2022. Everything was fine. Then they added a new Windows 10 workstation with 64-bit Excel. (All previously existing workstations are running 32-bit Office.) They ran an FR Balance Sheet on the new workstation, and it was out of balance. They ran the same BS on a different workstation, and everything was there, balanced. User login to Accpac made no difference. I logged in remotely to verify - same FR form file run with the same parameters for the same period returned a statement with missing data, resulting in an out of balance statement. We uninstalled Office and re-installed it as 32-bit. Issue resolved.

Hi Jim,

Thanks for sharing these details. Forwarded them onto our Sage 300 ERP support team who wasn't able to replicated the issue. They had the same balance sheet results in both the 32 vs 64 bit versions of Excel. If you come across this again, the team would be happy to open a support ticket to look into this further.

Warm Regards,

Erzsi

I have experienced the same issue with excel 64bit, when running balance sheet in FR designer on 64bit excel, report balanced, running balance sheet from Print Financial statements icon, it did not balance, so is a problem with the print icon process.

I recently had insufficient memory notification from Excel and decided to replace 32 bit office with 64-bit. Used the MS checking program to see if my excel files were 64-bit compatible and they were, with exception of 1 old unused file. Subsequent installation of 64-bit version worked well with my preferences/addins retained but many of my files gave catastrophic error on opening. On internet I see references to incompatibility of Active X buttons etc between 32 and 64 bit versions and think this is the cause - I use these. I also see some recommendations for programming these for both versions but that is a poor work-around. Is there anywhere where there is a clear explanation of what is and what is not compatible between versions. Otherwise I see Office 64-bit as being basically incompatible with most of the world.

You should write a code (in the 32 bit version, to avoid crashes) to replace all those active x buttons with shapes, you can detect the existing button position and size, even what macro is called from that button.

Having reinstalled 32 bit I have got over mem warnings and all works. Nonetheless, I would prefer to work with 64 bit as that's the future...Technically better etc. Will be trying your recommendation out in due course.

I am trying to set up a new connection to a csv file using the Transform tool. When I attempt to create the connection, Toad throws the the error: "Toad Data Point 4.0 is a 32-bit application. The 32-bit version of Microsoft Excel is required for compatibility with this feature..." But I DO have 32-bit Office 2016 installed. Any idea why this is happening?

The error message is confusing. We have changed this message in TDP 4.0.1. It usually means that you have Excel 2016 or Office 365. These two versions do not ship the ODBC driver needed to connect to csv or excel. Press on the hyperlink in the message and install the 32-bit access engine. This will resolve the issue

Decimal notation describes numbers using the digits 1 through 10. Binary notation describes them using just two digits, 1 and 0, where each bit in a string represents a power of 2. The right-most bit represents 2 raised to the power of 0, the next right-most bit represents 2 raised to the power of 1, and each remaining digit represents double the previous one's quantity. Microsoft Excel converts from binary to decimal notation using the BIN2DEC function and from decimal to binary using the DEC2BIN function.

3a8082e126