PC Review


Reply
Thread Tools Rate Thread

cannot have memo,ole or hyperlink object in aggregate argument

 
 
inungh
Guest
Posts: n/a
 
      1st Nov 2011
I have an application using SQL Server as backend and some of users
use Winodws XP and some using Windows 7.

My query works on Windows XP machine, but Windows 7 get error message

"cannot have memo,ole or hyperlink object in aggregate argument "

Any possiibility that Windows XP works but Windows 7 get above error
message?


Your help is great appreciated,


iccsi

 
Reply With Quote
 
 
 
 
Bob Barrows
Guest
Posts: n/a
 
      3rd Nov 2011
inungh wrote:
> I have an application using SQL Server as backend and some of users
> use Winodws XP and some using Windows 7.
>
> My query works on Windows XP machine, but Windows 7 get error message
>
> "cannot have memo,ole or hyperlink object in aggregate argument "
>
> Any possiibility that Windows XP works but Windows 7 get above error
> message?
>

Not really. If there is indeed a "memo,ole or hyperlink" column being
aggregated by your query, it should fail regardless of the Windows platform
the query is being executed from.
I would more suspect different versions of Access on each client, and one
version is recognizing one of the columns in your query either correctly or
incorrectly as the case may be.
Your first step is to identify the column that is causing the error.


 
Reply With Quote
 
inungh
Guest
Posts: n/a
 
      6th Nov 2011
On Nov 3, 5:28*pm, "Bob Barrows" <reb01...@NOSPAMyahoo.com> wrote:
> inungh wrote:
> > I have an application using SQL Server as backend and some of users
> > use Winodws XP and some using Windows 7.

>
> > My query works on Windows XP machine, but Windows 7 get error message

>
> > "cannot have memo,ole or hyperlink object in aggregate argument "

>
> > Any possiibility that Windows XP works but Windows 7 get above error
> > message?

>
> Not really. If there is indeed a "memo,ole or hyperlink" column being
> aggregated by your query, it should fail regardless of the Windows platform
> the query is being executed from.
> I would more suspect different versions of Access on each client, and one
> version is recognizing one of the columns in your query either correctly or
> incorrectly as the case may be.
> Your first step is to identify the column that is causing the error.


Thanks for helping,
Yes, it is what I thought.
All my users use same MS Access and only Windows 7 users get error
message.
I just change my stored procedures to return zero instead of null
value then Windows 7 machines work.
it seems that Windows 7 and Windows XP have different way to read null
value.


Thanks again for helping,


iccsi
 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off



Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 03:49 AM.