J
John Marshall, MVP
Dave
I reccomend not listening to these Mvp-Mdb faeiries.
They need to start preaching the good word of ADP.
One of the MVPs strong points is that they are NOT evangelists.
John... Visio MVP
Dave
I reccomend not listening to these Mvp-Mdb faeiries.
They need to start preaching the good word of ADP.
Tony Toews said:Oh, sorry, yes, but Aaron insists on stating ADPs are superior for
everything. Which they are not. They have their purpose in life but
their superiority is not at all evident.
I haven't worked with the A2003 installer and have no experience with
C# so I'm unable to answer your exact question.
How are you distributing updates? By using the runtime installer or
your own method? I'd suggest, as I think Arvin does, using your own
method once the initial version is on the client system by putting a
field in a table in the FE with the version number. Then, within
your app, interrogating the CD to see if it has a valid and newer MDB
on it. If so copy it.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony Toews said:Oh, sorry, yes, but Aaron insists on stating ADPs are superior for
everything. Which they are not. They have their purpose in life but
their superiority is not at all evident.
I haven't worked with the A2003 installer and have no experience with
C# so I'm unable to answer your exact question.
How are you distributing updates? By using the runtime installer or
your own method? I'd suggest, as I think Arvin does, using your own
method once the initial version is on the client system by putting a
field in a table in the FE with the version number. Then, within
your app, interrogating the CD to see if it has a valid and newer MDB
on it. If so copy it.
Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
[email protected] said:Half-- 2/3rds of the frequency of versioning can be avoided by choosing
the right architecture.
[email protected] said:I just use ADP and it's a LOT easier to deal with.
I have multiple version of stuff in DEV
APPNAME_20051019
APPNAME_20051020
if i need to make a new version in the middle of the day, i put a _8pm
at the end of it
[email protected] said:THE BOTTOM LINE IS THAT YOU HAVE 400kb FILES INSTEAD OF 50MB FILES.
SO YOU CAN AFFORD TO KEEP MULTIPLE VERSIONS
YOU CAN EMAIL ADP
YOU CAN DOWNLOAD ADP FROM A WEBSITE
[email protected] said:you cant email a mdb
it's TOO BIG and EVERYONE KNOWS YOU CANT RUN A LINKED MDB ACROSS A
NETWORK
like you have a column named EmployeePayRate and it has nulls.
You want to wrap a EmployeePayRate: NZ(EmployeePayRate, 0)
oh-- but wait a second; MDB is too stupid to let you reuse names
And MDBs work just fine across a network. With a few things you have
to be wary of. But I have a client with 25 users running against an
MDB.
Tony
Shannon McCord said:I have an mdb on a network share (backend on an SQL 2000 server, frontend is
Access MDB with linked tables) that is accessed by a max of 5 people. I
haven't had any trouble so far, but I am always interested in knowing about
potential problems.
Could you list the things I should be wary of? I looked on your web page,
(http://www.granite.ab.ca/accsmstr.htm) but did not find any information
(but lots of other interesting info).