M
magmike
2002 is what I have loaded. However, I think I created this database
in 2003, which is why (I think) it wants the 11.0 reference.
So I need to copy over the entire Office11 folder then?
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an alternative browser.
You should upgrade or use an alternative browser.
2002 is what I have loaded. However, I think I created this database
in 2003, which is why (I think) it wants the 11.0 reference.
So I need to copy over the entire Office11 folder then?
M
magmike
2002 is what I have loaded. However, I think I created this database
in 2003, which is why (I think) it wants the 11.0 reference.
So I need to copy over the entire Office11 folder then?
Yep - I added the entire folder at /Program Files/Microsoft Office/
Office11/ from an Office 2003 install, and migically, my database
works again!
A
Access Developer
a a r o n . k e m p f @ g m a i l . c o m said:wow it sounds to me like linked databases are
a total pain in the ass for you, and you'd be
better if you kept your logic in SQL Server
Reference issues have nothing, nil, zip to do with the linked database; they
are a phenomenon of the front end / ui code. You can't do front end / ui
code "in SQL Server".
A
a a r o n . k e m p f
it could be a linked _DATABASE_. Aka a library database
A
a a r o n . k e m p f
re: You can't do front end / ui code "in SQL Server".
Yes, stored procedures are more powerful than queries in Jet.. and
that's most of the legwork in writing front ends.
And of course.. Reporting shouldn't happen in Access, it should happen
in Reporting Services--
so how about you shut the **** up when you don't know what you're
talking about? How is reporting not part of the front end?
Maybe instead of reinventing the wheel-- these people should lose the
training wheels and stop having random database problems.
Get rid of Jet and all the nuisances it creates.. Only ****ing retards
use Jet as a database
Yes, stored procedures are more powerful than queries in Jet.. and
that's most of the legwork in writing front ends.
And of course.. Reporting shouldn't happen in Access, it should happen
in Reporting Services--
so how about you shut the **** up when you don't know what you're
talking about? How is reporting not part of the front end?
Maybe instead of reinventing the wheel-- these people should lose the
training wheels and stop having random database problems.
Get rid of Jet and all the nuisances it creates.. Only ****ing retards
use Jet as a database
D
David-W-Fenton
I don't see how Michka's article applies.
Well, it does apply, because it's point is that you want to run code
in a context in which code is broken by a missing reference. That
means removing all ambiguity so that VBA is not using it's internal
reference structures to interpret the code.
I don't know what provides the Object data type definition, and
think I'd likely rewrite your code to specify no data type (so it
would be a variant). It does work with an implicit Variant type.
D
David-W-Fenton
"a a r o n . k e m p f @ g m a i l . c o m" <[email protected]>
wrote in
:
Wow, you are just outdoing yourself today with posts that reveal
your bottomless stupidity.
Free clue: VBA references have nothing at all to do with the data
store in use.
Free clue: nobody was talking about "linked databases."
Free clue: "linked databases" doesn't even mean anything in an
Access context.
Free clue: you are a complete idiot and your "contributions" to the
Access newsgroups lower the signal-to-noise ratio.
wrote in
:
wow it sounds to me like linked databases are a total pain in the
ass for you, and you'd be better if you kept your logic in SQL
Server
Wow, you are just outdoing yourself today with posts that reveal
your bottomless stupidity.
Free clue: VBA references have nothing at all to do with the data
store in use.
Free clue: nobody was talking about "linked databases."
Free clue: "linked databases" doesn't even mean anything in an
Access context.
Free clue: you are a complete idiot and your "contributions" to the
Access newsgroups lower the signal-to-noise ratio.
M
magmike
re: You can't do front end / ui code "in SQL Server".
Yes, stored procedures are more powerful than queries in Jet.. and
that's most of the legwork in writing front ends.
And of course.. Reporting shouldn't happen in Access, it should happen
in Reporting Services--
so how about you shut the **** up when you don't know what you're
talking about? How is reporting not part of the front end?
Maybe instead of reinventing the wheel-- these people should lose the
training wheels and stop having random database problems.
Get rid of Jet and all the nuisances it creates.. Only ****ing retards
use Jet as a database
Do you really think you matter? My problem is fixed in spite of your
input. Who the "f" are you anyway?
A
Access Developer
magmike said:Do you really think you matter? My
problem is fixed in spite of your
input. Who the "f" are you anyway?
He's a resident newsgroup troll, who uses SQL Server as a convenient subject
to interject himself into threads. He either knows little about Access
and/or repeatedly lies about it, and knows a lot less about SQL Server than
he fancies he does.
Larry
T
Tony Toews
Well, it does apply, because it's point is that you want to run code
in a context in which code is broken by a missing reference. That
means removing all ambiguity so that VBA is not using it's internal
reference structures to interpret the code.
I don't know what provides the Object data type definition, and
think I'd likely rewrite your code to specify no data type (so it
would be a variant). It does work with an implicit Variant type.
But the developer is the person running this code. Ahh, you mean if
the developer puts this in the distributed FE, with some code to put
the results somewhere else such as the clipboard, and asks the user to
run it.
Tony
--
Tony Toews, Microsoft Access MVP
Tony's Main MS Access pages - http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/
For a convenient utility to keep your users FEs and other files
updated see http://www.autofeupdater.com/
D
David-W-Fenton
He's a resident newsgroup troll, who uses SQL Server as a
convenient subject to interject himself into threads. He either
knows little about Access and/or repeatedly lies about it, and
knows a lot less about SQL Server than he fancies he does.
I think Aaron knows the name "SQL Server" and not much else.
D
David-W-Fenton
But the developer is the person running this code. Ahh, you mean
if the developer puts this in the distributed FE, with some code
to put the results somewhere else such as the clipboard, and asks
the user to run it.
Or the developer ends up with broken references and tries to run the
code.
From my point of view, anything involved with enumerating references
has to be completely disambiguated, or it won't run if there's a
broken reference. Given that you're checking the IsBroken property,
it seems obvious to me that you must disambiguate everything.
Otherwise, the code simply won't be able to run.
A
a a r o n . k e m p f
David;
If you don't even know what the phrase 'library database' is then you
don't know jack shit about Access.
It's sort of like a DLL.
-Aaron
If you don't even know what the phrase 'library database' is then you
don't know jack shit about Access.
It's sort of like a DLL.
-Aaron