Quiz połączony z przewodnikiem · Średni Poziom
Jak pisać skrypty i makra w arkuszach kalkulacyjnych za pomocą quizu AI
Sprawdź, kiedy używać skryptów zamiast formuł, jak pisać bezpieczne żądania VBA i Apps Script oraz jak testować pocztę e-mail i makra czyszczące bez utraty danych.
Pytanie 1 z 8
Which task calls for a script rather than a formula?
Podgląd każdego pytania8 pytania
Odpowiedzi i wyjaśnienia pojawiają się w miarę rozwiązywania quizu.
- Which task calls for a script rather than a formula?
- Totaling a column of sales
- Looking up a price from a table
- Emailing every person whose status is Approved
- Formatting a number as currency
- What language does Google Sheets use for scripts?
- VBA
- Apps Script, which is JavaScript-based
- Python
- Office Scripts only
- Why does the guide stress testing Excel macros on a copy of the file?
- Macro changes generally cannot be undone with Ctrl+Z
- Copies run macros faster
- Excel refuses to run macros on original files
- The AI cannot read the original file
- What is the safest first test for a script that sends emails?
- Send to the whole list at once to save time
- Turn off the authorization prompt
- Run it on a sheet with no data
- Send only to yourself first, or list recipients before sending
- Why should a macro delete rows from the bottom up?
- VBA syntax requires it
- Deleting from the top shifts row numbers and causes rows to be skipped
- The bottom rows are always blank
- It avoids hitting email quotas
- What is the most efficient way to process many cells in Apps Script?
- Call getValue and setValue once for each cell
- Write a separate script for each row
- Read with getValues, process in memory, then write back with setValues
- Refresh the sheet after every change
- How can a script avoid redoing work if it stops partway and is run again?
- Mark each processed row, for example by writing "Sent" in a status column
- Delete the script after each run
- Ask Google to raise the quota
- Hide rows once they are processed
- According to the guide, where does the real risk of macros come from?
- The .xlsm file extension itself
- Adding comments to the code
- Using time-driven triggers
- Running code you do not understand, especially in files from strangers