sloan
10/25/2007 2:27:00 PM
I think calling it "Access Database" or "Jet database" may be a little
picky, esp for the original poster who we're trying to help, and not pick at
exact syntaxes.
I'm not going to argue whether you're right or wrong, because ... you are
"right".
And yes, you are right that you don't have to have the program installed to
work with a Jet database. But it makes it much more complicated.
You can create tables through code, and relationships, but my guess is that
most people who are considering using a Jet database, are still at the level
of creating Tables via the GUI of the program, and not via code.
So for the OP, I apologize miscueing on a few of my syntaxes, but I hope my
posts have tried to help your situation.
...
Access...I'm sorry....Jet databases ... are NOT true RDBMS, like Sql Server
or Oracle or etc, etc.
But sometimes they make sense. Or if you plan correctly, you can start
there, but still move up to another database.
"Armin Zingler" <az.nospam@freenet.de> wrote in message
news:O1zFjCwFIHA.700@TK2MSFTNGP05.phx.gbl...
> "Scott M." <s-mar@nospam.nospam> schrieb
>> >
>> > Access is two things at the same time. So you gotta distinquish.
>>
>> Well, actually no, it's not - so you don't.
>
> I think it is important to distinguish. Some people think, using the Jet
> requires Access being installed.
>
>> > There's the database, Access. This is when you put tables in
>> > there, like Employee
>> > Department
>> > JobTitles
>>
>> No, that's actually a JET database. There is actually no such real
>> thing as an "Access database". Sure, people call it that, but it's
>> really a JET database.
>
> An MDB file has always been called an "Access database". I'd still call an
> MDB file being in Access database format.
>
>
> Armin