Active X

i'm trying to research this question and i'm coming to a
dead end.
Question is:
Will my ms db active x work on ms sql server when it is
upsize/convert or whatnot?
reason why i need active x to work is... my whole
database on access 2000 is based on the active x
component. This component is like a "find" button where
search for the source data embedded in the table.
so can someone tell me if they have tried converting or
making active x from the db to sql to work?
even microsoft technical phone line can't help me or the
search function on //support.microsoft.com can't locate
this topic.
thank you for all your helpYou have to understand that Access is not the same as SQL Server. Your
ActiveX component is not likely to work with SQL Server without being
changed because there are no Forms to launch from in SQL Server. You'll
probably probably need to load it into a client development tool like VB.
Even then, the table connection semmantics might need to change, depending
on how the Active X component is designed.
You'd need to provide a lot more information about what this ActiveX
component actually does for us to provide much more feedback than this.
Regards,
Greg Linwood
SQL Server MVP
"Confused" <anonymous@.discussions.microsoft.com> wrote in message
news:376201c42987$d4de51c0$a601280a@.phx.gbl...
> i'm trying to research this question and i'm coming to a
> dead end.
> Question is:
> Will my ms db active x work on ms sql server when it is
> upsize/convert or whatnot?
> reason why i need active x to work is... my whole
> database on access 2000 is based on the active x
> component. This component is like a "find" button where
> search for the source data embedded in the table.
> so can someone tell me if they have tried converting or
> making active x from the db to sql to work?
> even microsoft technical phone line can't help me or the
> search function on //support.microsoft.com can't locate
> this topic.
> thank you for all your help|||Aaahhh.. thank you for the reply and answer. That is
what i've been trying to research and get an answer on
that front.
Since ActiveX component is not likely to work on SQL
server, and you state that i need to load it into a client
development too like VB... is the client development
integrated with SQL server? or is that program an add-on
like an activex component?
How does my ActiveX function in access db is on the form
layout. It pulls data source files in the table i
embedded on access db tables. The activeX i use for my
database is voloview, it is a 3rd autocad image/map
program (i.e. browser to nag. maps and images) but at the
same time, it pulls up data source information. Like
customer information, address or data from the table.
The ActiveX is very crucial, because it runs the whole
database source and pulls information from different
location all at once.
If SQL don't have a form layout, then how can one enter
data into a server'
My company is trying to be more on the hi-end of the
technology. So they want to move the database to a server
base since microsoft access can't hold more than couple of
user on the same program or database at once (lag time and
information not being updated in a timeframe). So they
figure SQL is the way to do it.
What is your recommendation for me to combat this
situation'
FYI: reason why i haven't used out programs like mysql or
vendors outside who can do all the database programming to
make this work is because the company is on a budget and
they figure if microsoft access is treating them great on
the database (ie. no problem entering datas, etc..) they
figure they should stick with a trusted source.
Thank you for all your help
>--Original Message--
>You have to understand that Access is not the same as SQL
Server. Your
>ActiveX component is not likely to work with SQL Server
without being
>changed because there are no Forms to launch from in SQL
Server. You'll
>probably probably need to load it into a client
development tool like VB.
>Even then, the table connection semmantics might need to
change, depending
>on how the Active X component is designed.
>You'd need to provide a lot more information about what
this ActiveX
>component actually does for us to provide much more
feedback than this.
>Regards,
>Greg Linwood
>SQL Server MVP
>"Confused" <anonymous@.discussions.microsoft.com> wrote in
message
>news:376201c42987$d4de51c0$a601280a@.phx.gbl...
>> i'm trying to research this question and i'm coming to a
>> dead end.
>> Question is:
>> Will my ms db active x work on ms sql server when it is
>> upsize/convert or whatnot?
>> reason why i need active x to work is... my whole
>> database on access 2000 is based on the active x
>> component. This component is like a "find" button where
>> search for the source data embedded in the table.
>> so can someone tell me if they have tried converting or
>> making active x from the db to sql to work?
>> even microsoft technical phone line can't help me or the
>> search function on //support.microsoft.com can't locate
>> this topic.
>> thank you for all your help
>
>.
>|||SQL Server doesn't have a server side Forms tool - it focusses on providing
the database components (think of the Tables / Queries tabs in Access). It
assumes you're using another tool to develop the client forms etc.
I'm not sure if you've taken this into account yet, but you can actually use
Access as the front end forms environment for SQL Server. The way you do
this is by "splitting" the tables & queries from the Access database into
SQL Server tables / views, link them to the Access db & the forms should
then work as normal. This often provides greater scalability than a pure
Access solution (what you've got now) and doesn't require changes to the
Access forms - they just keep working as is.
Given you've mentioned cost savings, you might consider putting the SQL
Server side of things into MSDE which is a freely distributed version of the
basic SQL Server features.
Splitting Access tables to SQL Server provides increased scalability over
pure Access but isn't as good as a full port to a client / server SQL Server
implementation, but it might give you what you're after..
HTH
Regards,
Greg Linwood
SQL Server MVP
"Confused" <anonymous@.discussions.microsoft.com> wrote in message
news:38f301c42990$5d2df960$a501280a@.phx.gbl...
> Aaahhh.. thank you for the reply and answer. That is
> what i've been trying to research and get an answer on
> that front.
> Since ActiveX component is not likely to work on SQL
> server, and you state that i need to load it into a client
> development too like VB... is the client development
> integrated with SQL server? or is that program an add-on
> like an activex component?
> How does my ActiveX function in access db is on the form
> layout. It pulls data source files in the table i
> embedded on access db tables. The activeX i use for my
> database is voloview, it is a 3rd autocad image/map
> program (i.e. browser to nag. maps and images) but at the
> same time, it pulls up data source information. Like
> customer information, address or data from the table.
> The ActiveX is very crucial, because it runs the whole
> database source and pulls information from different
> location all at once.
> If SQL don't have a form layout, then how can one enter
> data into a server'
> My company is trying to be more on the hi-end of the
> technology. So they want to move the database to a server
> base since microsoft access can't hold more than couple of
> user on the same program or database at once (lag time and
> information not being updated in a timeframe). So they
> figure SQL is the way to do it.
> What is your recommendation for me to combat this
> situation'
> FYI: reason why i haven't used out programs like mysql or
> vendors outside who can do all the database programming to
> make this work is because the company is on a budget and
> they figure if microsoft access is treating them great on
> the database (ie. no problem entering datas, etc..) they
> figure they should stick with a trusted source.
> Thank you for all your help
> >--Original Message--
> >You have to understand that Access is not the same as SQL
> Server. Your
> >ActiveX component is not likely to work with SQL Server
> without being
> >changed because there are no Forms to launch from in SQL
> Server. You'll
> >probably probably need to load it into a client
> development tool like VB.
> >Even then, the table connection semmantics might need to
> change, depending
> >on how the Active X component is designed.
> >
> >You'd need to provide a lot more information about what
> this ActiveX
> >component actually does for us to provide much more
> feedback than this.
> >
> >Regards,
> >Greg Linwood
> >SQL Server MVP
> >
> >"Confused" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:376201c42987$d4de51c0$a601280a@.phx.gbl...
> >> i'm trying to research this question and i'm coming to a
> >> dead end.
> >>
> >> Question is:
> >>
> >> Will my ms db active x work on ms sql server when it is
> >> upsize/convert or whatnot?
> >>
> >> reason why i need active x to work is... my whole
> >> database on access 2000 is based on the active x
> >> component. This component is like a "find" button where
> >> search for the source data embedded in the table.
> >>
> >> so can someone tell me if they have tried converting or
> >> making active x from the db to sql to work?
> >>
> >> even microsoft technical phone line can't help me or the
> >> search function on //support.microsoft.com can't locate
> >> this topic.
> >>
> >> thank you for all your help
> >
> >
> >.
> >|||Hi Greg,
Thank you for all your help. Is there a book you could
recommend on reading up on this process? I'm new to SQL
and the pathform it provides but all your help was very
appreciated.
Mike
>--Original Message--
>SQL Server doesn't have a server side Forms tool - it
focusses on providing
>the database components (think of the Tables / Queries
tabs in Access). It
>assumes you're using another tool to develop the client
forms etc.
>I'm not sure if you've taken this into account yet, but
you can actually use
>Access as the front end forms environment for SQL Server.
The way you do
>this is by "splitting" the tables & queries from the
Access database into
>SQL Server tables / views, link them to the Access db &
the forms should
>then work as normal. This often provides greater
scalability than a pure
>Access solution (what you've got now) and doesn't require
changes to the
>Access forms - they just keep working as is.
>Given you've mentioned cost savings, you might consider
putting the SQL
>Server side of things into MSDE which is a freely
distributed version of the
>basic SQL Server features.
>Splitting Access tables to SQL Server provides increased
scalability over
>pure Access but isn't as good as a full port to a
client / server SQL Server
>implementation, but it might give you what you're after..
>HTH
>Regards,
>Greg Linwood
>SQL Server MVP
>"Confused" <anonymous@.discussions.microsoft.com> wrote in
message
>news:38f301c42990$5d2df960$a501280a@.phx.gbl...
>> Aaahhh.. thank you for the reply and answer. That is
>> what i've been trying to research and get an answer on
>> that front.
>> Since ActiveX component is not likely to work on SQL
>> server, and you state that i need to load it into a
client
>> development too like VB... is the client development
>> integrated with SQL server? or is that program an add-
on
>> like an activex component?
>> How does my ActiveX function in access db is on the form
>> layout. It pulls data source files in the table i
>> embedded on access db tables. The activeX i use for my
>> database is voloview, it is a 3rd autocad image/map
>> program (i.e. browser to nag. maps and images) but at
the
>> same time, it pulls up data source information. Like
>> customer information, address or data from the table.
>> The ActiveX is very crucial, because it runs the whole
>> database source and pulls information from different
>> location all at once.
>> If SQL don't have a form layout, then how can one enter
>> data into a server'
>> My company is trying to be more on the hi-end of the
>> technology. So they want to move the database to a
server
>> base since microsoft access can't hold more than couple
of
>> user on the same program or database at once (lag time
and
>> information not being updated in a timeframe). So they
>> figure SQL is the way to do it.
>> What is your recommendation for me to combat this
>> situation'
>> FYI: reason why i haven't used out programs like mysql
or
>> vendors outside who can do all the database programming
to
>> make this work is because the company is on a budget and
>> they figure if microsoft access is treating them great
on
>> the database (ie. no problem entering datas, etc..) they
>> figure they should stick with a trusted source.
>> Thank you for all your help
>> >--Original Message--
>> >You have to understand that Access is not the same as
SQL
>> Server. Your
>> >ActiveX component is not likely to work with SQL Server
>> without being
>> >changed because there are no Forms to launch from in
SQL
>> Server. You'll
>> >probably probably need to load it into a client
>> development tool like VB.
>> >Even then, the table connection semmantics might need
to
>> change, depending
>> >on how the Active X component is designed.
>> >
>> >You'd need to provide a lot more information about what
>> this ActiveX
>> >component actually does for us to provide much more
>> feedback than this.
>> >
>> >Regards,
>> >Greg Linwood
>> >SQL Server MVP
>> >
>> >"Confused" <anonymous@.discussions.microsoft.com> wrote
in
>> message
>> >news:376201c42987$d4de51c0$a601280a@.phx.gbl...
>> >> i'm trying to research this question and i'm coming
to a
>> >> dead end.
>> >>
>> >> Question is:
>> >>
>> >> Will my ms db active x work on ms sql server when it
is
>> >> upsize/convert or whatnot?
>> >>
>> >> reason why i need active x to work is... my whole
>> >> database on access 2000 is based on the active x
>> >> component. This component is like a "find" button
where
>> >> search for the source data embedded in the table.
>> >>
>> >> so can someone tell me if they have tried converting
or
>> >> making active x from the db to sql to work?
>> >>
>> >> even microsoft technical phone line can't help me or
the
>> >> search function on //support.microsoft.com can't
locate
>> >> this topic.
>> >>
>> >> thank you for all your help
>> >
>> >
>> >.
>> >
>
>.
>|||As I recall, there's a Database Splitter command under something like Tools
/ Database Utilities which does the splitting for you. From there, you
replace the file with the tables for a database with ODBC links to the SQL
back end.
I don't know of a book myself as I don't use Access much, but I'm sure you'd
get good help from the people in the Access newsgroups. A google search
would probably provide you with lots of info as well.
Regards,
Greg Linwood
SQL Server MVP
"Confused" <anonymous@.discussions.microsoft.com> wrote in message
news:475c01c42bb2$45c30bc0$a101280a@.phx.gbl...
> Hi Greg,
> Thank you for all your help. Is there a book you could
> recommend on reading up on this process? I'm new to SQL
> and the pathform it provides but all your help was very
> appreciated.
> Mike
> >--Original Message--
> >SQL Server doesn't have a server side Forms tool - it
> focusses on providing
> >the database components (think of the Tables / Queries
> tabs in Access). It
> >assumes you're using another tool to develop the client
> forms etc.
> >
> >I'm not sure if you've taken this into account yet, but
> you can actually use
> >Access as the front end forms environment for SQL Server.
> The way you do
> >this is by "splitting" the tables & queries from the
> Access database into
> >SQL Server tables / views, link them to the Access db &
> the forms should
> >then work as normal. This often provides greater
> scalability than a pure
> >Access solution (what you've got now) and doesn't require
> changes to the
> >Access forms - they just keep working as is.
> >
> >Given you've mentioned cost savings, you might consider
> putting the SQL
> >Server side of things into MSDE which is a freely
> distributed version of the
> >basic SQL Server features.
> >
> >Splitting Access tables to SQL Server provides increased
> scalability over
> >pure Access but isn't as good as a full port to a
> client / server SQL Server
> >implementation, but it might give you what you're after..
> >
> >HTH
> >
> >Regards,
> >Greg Linwood
> >SQL Server MVP
> >
> >"Confused" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:38f301c42990$5d2df960$a501280a@.phx.gbl...
> >> Aaahhh.. thank you for the reply and answer. That is
> >> what i've been trying to research and get an answer on
> >> that front.
> >>
> >> Since ActiveX component is not likely to work on SQL
> >> server, and you state that i need to load it into a
> client
> >> development too like VB... is the client development
> >> integrated with SQL server? or is that program an add-
> on
> >> like an activex component?
> >>
> >> How does my ActiveX function in access db is on the form
> >> layout. It pulls data source files in the table i
> >> embedded on access db tables. The activeX i use for my
> >> database is voloview, it is a 3rd autocad image/map
> >> program (i.e. browser to nag. maps and images) but at
> the
> >> same time, it pulls up data source information. Like
> >> customer information, address or data from the table.
> >>
> >> The ActiveX is very crucial, because it runs the whole
> >> database source and pulls information from different
> >> location all at once.
> >>
> >> If SQL don't have a form layout, then how can one enter
> >> data into a server'
> >>
> >> My company is trying to be more on the hi-end of the
> >> technology. So they want to move the database to a
> server
> >> base since microsoft access can't hold more than couple
> of
> >> user on the same program or database at once (lag time
> and
> >> information not being updated in a timeframe). So they
> >> figure SQL is the way to do it.
> >>
> >> What is your recommendation for me to combat this
> >> situation'
> >>
> >> FYI: reason why i haven't used out programs like mysql
> or
> >> vendors outside who can do all the database programming
> to
> >> make this work is because the company is on a budget and
> >> they figure if microsoft access is treating them great
> on
> >> the database (ie. no problem entering datas, etc..) they
> >> figure they should stick with a trusted source.
> >>
> >> Thank you for all your help
> >> >--Original Message--
> >> >You have to understand that Access is not the same as
> SQL
> >> Server. Your
> >> >ActiveX component is not likely to work with SQL Server
> >> without being
> >> >changed because there are no Forms to launch from in
> SQL
> >> Server. You'll
> >> >probably probably need to load it into a client
> >> development tool like VB.
> >> >Even then, the table connection semmantics might need
> to
> >> change, depending
> >> >on how the Active X component is designed.
> >> >
> >> >You'd need to provide a lot more information about what
> >> this ActiveX
> >> >component actually does for us to provide much more
> >> feedback than this.
> >> >
> >> >Regards,
> >> >Greg Linwood
> >> >SQL Server MVP
> >> >
> >> >"Confused" <anonymous@.discussions.microsoft.com> wrote
> in
> >> message
> >> >news:376201c42987$d4de51c0$a601280a@.phx.gbl...
> >> >> i'm trying to research this question and i'm coming
> to a
> >> >> dead end.
> >> >>
> >> >> Question is:
> >> >>
> >> >> Will my ms db active x work on ms sql server when it
> is
> >> >> upsize/convert or whatnot?
> >> >>
> >> >> reason why i need active x to work is... my whole
> >> >> database on access 2000 is based on the active x
> >> >> component. This component is like a "find" button
> where
> >> >> search for the source data embedded in the table.
> >> >>
> >> >> so can someone tell me if they have tried converting
> or
> >> >> making active x from the db to sql to work?
> >> >>
> >> >> even microsoft technical phone line can't help me or
> the
> >> >> search function on //support.microsoft.com can't
> locate
> >> >> this topic.
> >> >>
> >> >> thank you for all your help
> >> >
> >> >
> >> >.
> >> >
> >
> >
> >.
> >