David W. Fenton wrote:
Salad <oi*@vinegar.comwrote in
news:13*************@corp.supernews.com:
>>Had 1 more column in the database window called "Last Compiled"
When you compile the front end all of the "Modified" timestamps
reflect the last date/time of the compile...not when the developer
modified the files.
This destroys the history of work a developer did.
If I had any pull with MS I'd request they make a new column for
compile dates. I could compare the last dates of compile to the
last modified file.
I don't know if you find it annoying you can't have a history of
changes. I do.
This is a consequence of the implementation of the VBE and the
monolithic save model for the VBA project that was first introduced
in A2K.
That may be a consequence. But it would be nice to have an extra date
column so history isn't lost. The guys who write Access aren't
developing with Access.
There's another things I'd also change. For example, when going to the
design wizard of a form all tables and queries are mixed. Tables are
preceeded with the word Tables, queries with Queries. But if you go
into Query/New and click on Add tables the tables have a tab, queries
another. That is so much nicer. If you are going to tell us what is a
table and what is a query then put it in a separate column and put the
object name first.
>
It was just a stupid idea, and I can't understand the logic behind
it. No explanation that has ever been given ("it's to decrease the
incidence of corruption." Eh? How does storing it all in a huge BLOB
field instead of a whole bunch of individual records, one for each
module, decrease the incidence of corruption?) makes any sense to me
at all.
I suppose Michka could answer that.
I don't even like the object type options displayed vertically and the
action type displayed horizontally in the database window. It was like
someone went of their way to "shake things up". I liked them like they
were in '97.
Like the war in Iraq, nobody asked for my opinion.