Application distribution

[paddymx]

I am working on a DB that I would like to share. I have Access 2003 and Visual Studio Tools. Several years ago I was thinking about the same thing and had a problem with Windows Update making changes that would require user intervention. Not liking that I decided to forget it.



As I understand it now, MS has put everything in the "cloud" and expects everyone to use their latest versions(runtime etc.). Being "tight" and happy with 2003 I won't be getting the NEW versions of Access.

Here's the question. What problems will the end user encounter if I distribute using my 2003 MDE and Tools(via .zip)? I think my only other option would be to require the user to have 2003 and hope for the best, but, that limits those who would be able to use it.

Would appreciate any input.

Thanks

Patrick

[GraeagleBill]

Patrick,
You shouldn't have any problems distributing a A2003 based mde along with related files and folders as long as your client isn't currently running A2000 AND your mde DOES NOT have features un-supported in A2000, e.g., OpenArgs to Reports. I assume you wouldn't distribute the backend mdb file other than mdb scaffolding with a new install. If your client DOES NOT have Access installed, then you simply have to give aid in getting the FREE runtime module from Microsoft.
Bill

[paddymx]

Patrick,
You shouldn't have any problems distributing a A2003 based mde along with related files and folders as long as your client isn't currently running A2000 AND your mde DOES NOT have features un-supported in A2000, e.g., OpenArgs to Reports. I assume you wouldn't distribute the backend mdb file other than mdb scaffolding with a new install. If your client DOES NOT have Access installed, then you simply have to give aid in getting the FREE runtime module from Microsoft.
Bill

Thanks for the fast response.
I do have OpenArgs in Reports and in forms so I guess I need to re-think them. Any other glitches?

" backend mdb file other than mdb scaffolding". This will NOT be a split DB but I am not familiar with the term "scaffolding".
" If your client DOES NOT have Access installed". Does this mean that the user will need instructions for the "runtime" (via the cloud) even though It would be included via VS Tools? You see this is not for any "Client". I want to share this with the e-cig community as a "For Public Domain Use Only" . Therefore I am not planning on offering "Help Desk" access. That could get out of hand rather quickly. No way to know what the end user has on their machine. I was afraid I would run into these types of issues.

EDIT: I haven't done any Access for at least 10 yrs. so I'm still getting up to speed.

[GraeagleBill]

Sorry, my use of the term "scaffolding" is from the "old days". "Table structure and table/field relationships" is what I mean. That is, with a split database app, the backend is only installed with an initial release. Any field or table additions/updates must be carried out by the frontend app with due consideration to whatever data the end user has put into their DB. This usually would occur with version updates to the app.

If VS Tools includes the Runtime modules, then I wouldn't expect any problems there. I'm NOT familiar with VS Tools, so take my comment with due caution. (I am familiar with the SageKey deployment app. If VS Tools is like that then there ought not be any problem.)

[paddymx]

Sorry, my use of the term "scaffolding" is from the "old days". "Table structure and table/field relationships" is what I mean. That is, with a split database app, the backend is only installed with an initial release. Any field or table additions/updates must be carried out by the frontend app with due consideration to whatever data the end user has put into their DB. This usually would occur with version updates to the app.

If VS Tools includes the Runtime modules, then I wouldn't expect any problems there. I'm NOT familiar with VS Tools, so take my comment with due caution. (I am familiar with the SageKey deployment app. If VS Tools is like that then there ought not be any problem.)

No problem.

"Any field or table additions/updates must be carried out..." I'm afraid those types of modifications are above my pay grade. I'm self taught and dyslexic to boot. I've done client/server in the past but my abilities would only be in re-distributing the "Client side"(forms).

Back in the day, MS made you buy "Developers Tool Kit" (3.1/95/97) and then with 2003 you had to get VS Tools which included the "Developers Tool Kit" along with VB6. That was the straw that broke the camels back for me. The "Tools" are like SageKey and does much the same. I looked into it a long time ago but don't remember why I didn't get it. I think it was around the time MS went with their "Free Runtime" on the cloud.

Thanks for the assistance. I'll continue to work on it and see what I can come up with. Perhaps I can find a beta tester when I get done.

Patrick

[Old Goat]

Define "Visual Studio Tools". If you want to distribute a 2003 MDE to machines that do not have the full version of Access 2003, you will need a special version of "Visual Studio Tools" that is no longer available. Let me know if you need the exact name, and I'll log on to my work box and get it, but it is the "MS Access Developer Extensions for Access 2003" or something like that. Here it is: http://msdn.microsoft.com/en-us/office/aa905403.aspx

[paddymx]

Define "Visual Studio Tools". If you want to distribute a 2003 MDE to machines that do not have the full version of Access 2003, you will need a special version of "Visual Studio Tools" that is no longer available. Let me know if you need the exact name, and I'll log on to my work box and get it, but it is the "MS Access Developer Extensions for Access 2003" or something like that. Here it is: http://msdn.microsoft.com/en-us/office/aa905403.aspx

Thanks, I've got the one which includes the MSO Access 2003 Developer Extensions with MSO Access runtime license. Got it back in 2003. Same one that was at the link. My fault for calling it "Developers Tool Kit"which was what it was called when you had to purchase it separately before the VS Tools package. The VS Tools I've got also included VB.net, SQL Server 2000.