Re: why>?

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

aaron.kempf@xxxxxxxxx wrote...
and for the record; yes; anything that excel touches involving
databases goes through jet.

i have found some vague ms references that say this; but it uses the
word DATA... which to me includes any cells entered on a work***.

I believe that this means that Excel uses an engine derived from jet.

Or it means JET evolved from Excel, since Excel existed as a product
before JET. Do you really believe Excel's methods for storing and
accessing cells either on disk (.xls files) or in memory hasn't evolved
from Excel 1.0, which was available on Macs in 1986?

Maybe you mean MS Query, which was the database access tool in Excel 5,
was based on JET. Probably so. But if you mean when SQL.REQUEST pulls
from a non-JET ODBC data source somehow JET is involved, then I'm not
prepared to take your word for it. Show some publicly available
information that says so.

FWIW, I ran the following zsh command under Cygwin in my Office11
directory,

strings -f * | grep -i JET

and this was all it produced:

ACWZDAT.MDT: Standard Jet DB
ACWZLIB.MDE: Standard Jet DB
ACWZLIB.MDE: JET_coltypNil
ACWZMAIN.MDE: Standard Jet DB
ACWZMAIN.MDE: JET_coltypNil
ACWZTOOL.MDE: Standard Jet DB
ACWZTOOL.MDE: JET_bitREPPartial
ACWZTOOL.MDE: JET_bitREPReadOnly
ACWZTOOL.MDE: JET_bitREPPreventDeletes
ACWZTOOL.MDE: JET_bitREPGlobal:
ACWZTOOL.MDE: JET_bitREPLocal
ACWZTOOL.MDE: JET_bitREPAnonymous
ACWZTOOL.MDE: stTypeJetBinary
ACWZTOOL.MDE: conErrNoJetSystemLz
ACWZTOOL.MDE: errJet
ACWZTOOL.MDE: wlib_JetCreateSystemDatabaseC
ACWZTOOL.MDE: UT_IJetColtypOfAccType
ACWZTOOL.MDE: iJetColtyp
ACWZTOOL.MDE: lJetErr
ACWZTOOL.MDE: lJetColtyp
ACWZTOOL.MDE: stJetRemoteTable
ACWZTOOL.MDE: JET_coltypNil
ACWZTOOL.MDE: wlib_JetCreateSystemDatabaseC
ACWZTOOL.MDE: UT_IJetColtypOfAccType
ACWZTOOL.MDE: iJetColtyp
ACWZTOOL.MDE: stTypeJetBinary
ACWZTOOL.MDE: lJetColtyp
ACWZUSR.MDT: Standard Jet DB
MSACCESS.EXE: jeterr40.chm
MSACCESS.EXE: jetsql40.chm
MSACCESS.EXE: PromptDAPJetLocalPaths
MSACCESS.EXE: JETESLoadProjectTypeLib
MSACCESS.EXE: msjet40.dll
MSACCESS.EXE: +Jet)R
MSJSPP40.DLL: JET IISAM
MSPUB.EXE: hjety
MSPUB.EXE: Compatible with HPPCL5MS,HP LaserJet IIISi
MSPUB.EXE: Compatible with HPPCL5MS,HP LaserJet IIISi
MSPUB.EXE: Compatible with HPPCL5MS,HP LaserJet IIISi
UTILITY.MDA: Standard Jet DB
WINWORD.EXE: Sujet

Looks to me like only the Access files contain any references to JET.

Now DLLs that Excel calls could in turn call JET-related DLLs, but I'll
leave that for you to establish.

I dont understand your question; i will look into it at lunch.
I haven't ever had a problem with anything involving date ranges.

No! Really?!

Seems to be a lot I do with which you're unfamiliar.

for starters; i have drilldown.. double-click on year and it gives you
quaters or months-- or weeks-- anything you want.
....

If you've already calculated or collected the weekly figures, yes, you
have them. If you only have monthly figures, you don't have weekly
figures. You need to calculate them.

yes; i do create a single date table that i use for translating dates;
including fiscal periods; etc.

It can be table-driven, but it's unnecessary and storage-redundant
since dates stored either as number of days from 1-Jan-1900 (with
traditional 29-Feb-1900 bug) or 1-Jan-1904 or number of seconds from
1-Jan-1970 00:00 GMT, you can calculate periods in terms of fractional
calendar months directly. There's no clear advantage to using tables
for this vs direct calculation.

but i dont even use the date datatype -- for a bunch of reasons-- in
most of my work because it's such a large and clunky datatype.
....

Dates, in Excel and Access, use 64 bits. Dates using short integers
would take 16 bits. Are you using short integers? How do you store
time?


And, of course, you skip over the interpolation calculation.

.

Quantcast