Mark Breen
marklbreen at gmail.com
Fri Jan 21 01:46:39 CST 2005
Hello Gustav and Lambert, Thank you Gustav, that sounds even more optimistic, we will do some testing and I will let the list know how we get one. Lambert, thanks for your caution, in our case we are calling stored procedures and passing back parameters so I will keep the list informed as to how we get on. Thanks again all, Mark On Thu, 20 Jan 2005 11:34:31 -0500, Heenan, Lambert <Lambert.Heenan at aig.com> wrote: > That may be so, but you can get other screwy effects if some newer > references are used. > > e.g. If you have an app. that references Outlook 97 and the user has Outlook > 98 or 2000+ installed, then any reports in the database will give problems. > Specifically, if you have a textbox on a report with a data source like > this... > > ="Printed " & Format(Now(),"ddd mmm-d"", ""yyyy h:nn am/pm") > > then this works fine for users with Outlook 97, but those with a later > version of Outlook will see nothing at all in the textbox. Instead you will > need two textboxes, one with > > ="Printed " as a data source, and the other with Now() and the format > property of the second textbox will need to be set to ddd", "mmm dd", "yyyy > hh:nn > > Note that there is no sign of any runtime error in this situation. The > textbox is simply not filled. > > Lambert > > > -----Original Message----- > > From: accessd-bounces at databaseadvisors.com > > [SMTP:accessd-bounces at databaseadvisors.com] On Behalf Of Gustav Brock > > Sent: Thursday, January 20, 2005 8:43 AM > > To: accessd at databaseadvisors.com > > Subject: Re: [AccessD] Calling ADO without having to roll out five > > hundrednewmdbs > > > > Hi Mark > > > > Typically a newer version will be accepted while and older will not. > > But only testing can determine this for sure. > > > > /gustav > > > > >>> marklbreen at gmail.com 20-01-2005 14:09:22 >>> > > > > My next concern (and I am not asking for help, just thinking out load) > > is the versions of ADO that we will reference. What happens if I > > reference ADO version 2.6 for example, but the user has a later or > > earlier version than the development machine? > > > > Do I need to programatically enumerate the references and check for > > "missing" and then programatically attempt to assign another version > > of ADO? Does not sound that pretty ! > > > > I am not too concerned about needing the latest version, all we are > > doing is calling an Oracle stored procedure and accepting output > > parameters (hence the need to ADO in the first place). > > > > -- > > AccessD mailing list > > AccessD at databaseadvisors.com > > http://databaseadvisors.com/mailman/listinfo/accessd > > Website: http://www.databaseadvisors.com > -- > AccessD mailing list > AccessD at databaseadvisors.com > http://databaseadvisors.com/mailman/listinfo/accessd > Website: http://www.databaseadvisors.com >