Re: It would be nice if MS did this
- From: Tom van Stiphout <no.spam.tom7744@xxxxxxx>
- Date: Wed, 17 Oct 2007 21:09:10 -0700
On Thu, 18 Oct 2007 00:10:25 GMT, "ARC" <PCESoft@xxxxxxxxxxxxxxx>
wrote:
However, if you read about the many restrictions for using SourceSafe
to store individual Access objects, that route is no longer very
attractive.
And storing SQL Server objects in SourceSafe: Ha!
-Tom.
I agree.. The dates are fairly meaningless, and I never use them. Pretty.
sure you need to use source code control to be able to track the modified
info.
"Salad" <oil@xxxxxxxxxxx> wrote in message
news:13hc90a2rercl3f@xxxxxxxxxxxxxxxxxxxxx
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.
- References:
- It would be nice if MS did this
- From: Salad
- Re: It would be nice if MS did this
- From: ARC
- It would be nice if MS did this
- Prev by Date: Re: It would be nice if MS did this
- Next by Date: Re: Migrating away from MS-Access
- Previous by thread: Re: It would be nice if MS did this
- Next by thread: Re: It would be nice if MS did this
- Index(es):
Relevant Pages
|
