I understand the designer in Reporting Services can import Access reports.
Today a customer asked me if it's possible to import reports on Great Plains
data written using FRX. Anybody know?
JimJames,
The FRX file is a Visual Fox file which is really a table. The format is
well documented but I am not aware of a direct conversion tool at this time.
I would suggest a repost on the Visual Fox newsgroup
microsoft.public.fox.vfp.reports.printing.
Best Regards,
--
David W. Grigsby
Grigsby Consulting LLC
http://www.grigsbyconsultingllc.com
This posting is provided "AS IS" with no warranties, and confers no rights.
"James Foye" <jimfoye2@.hotmail.com> wrote in message
news:%23Yo074YfEHA.3964@.TK2MSFTNGP12.phx.gbl...
> I understand the designer in Reporting Services can import Access reports.
> Today a customer asked me if it's possible to import reports on Great
Plains
> data written using FRX. Anybody know?
> Jim
>
Showing posts with label access. Show all posts
Showing posts with label access. Show all posts
Monday, March 26, 2012
Friday, March 23, 2012
Frustrated with two clients that can't connect...
I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev
"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev
"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.
Frustrated with two clients that can't connect...
I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.
Frustrated with two clients that can't connect...
I have a SQL server that I am trying to access from across a WAN. 1 machine
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.
of the 3 machines will connect ok, the other 2 machine's will not. The SQL
server is using Named Pipes. On all 3 machines I can do a net view
\\servername and have it come back ok. I've tried both SQL auth and Windows
auth and both work on the machine that can connect and both fail on the
machine's that won't.
How do you troubleshoot a client that won't connect?
Is there a SQL client configuration utility? If so how do I run it /
install it?
My debugging application allows me to get to a "Data Link Properties" dialog
that allows me to try settings. Can you get to this dialog on any machine?
How can I invoke it? I remember something about creating an empty file with
a specific extension and going to its properties but I may be thinking of
ODBC.
Any ideas?
Thanks,
SA Dev"SA Development" <nospam38925@.forme.com> wrote in message
news:3tCdnYtUxJwY793fRVn-1A@.valortelecom.com...
>I have a SQL server that I am trying to access from across a WAN. 1
>machine of the 3 machines will connect ok, the other 2 machine's will not.
>The SQL server is using Named Pipes. On all 3 machines I can do a net view
>\\servername and have it come back ok. I've tried both SQL auth and
>Windows auth and both work on the machine that can connect and both fail on
>the machine's that won't.
> How do you troubleshoot a client that won't connect?
> Is there a SQL client configuration utility? If so how do I run it /
> install it?
It's called "Client Network Utility". Install the SQL Tools from the SQL
Server CD, and make sure your client is using the same protocols, etc., as
the Server (use the Server Network Utility on the Server to determine this).
BTW, what version of SQL Server are you using? Are the 3 machines
configured similarly? Same Network protocols, same firewall settings (if
any), etc.?
> My debugging application allows me to get to a "Data Link Properties"
> dialog that allows me to try settings. Can you get to this dialog on any
> machine? How can I invoke it? I remember something about creating an
> empty file with a specific extension and going to its properties but I may
> be thinking of ODBC.
You can test your server connection from the ODBC Administrator by creating
an ODBC DSN in it and, when done, click on the Test button.
Is this an application you are developing or a pre-packaged app? If it's an
app you're developing, you might need to re-visit your connection string
settings. If it's a pre-packaged app, you will probably have to scan their
documentation for specific configuration info.
Frontpage and upsized db from Access to SQL 2000-difficult?
I currently have a database in Access 2000 that I wish to upsize to Sql 2000.
I have read about the upsize wizard. This sounds ideal. However, I have a
company intranet application developed based on the Access database. How
would I use the existing application to now connect to SQL. Is this
difficult? The intranet is still in its initial stages...and I have read that
sql would be better. We have Small Business Server 2003 so it comes with the
system. Is there a web site/page that might help me convert this website and
how to create a connection. I thought perhaps it would be best to try and
convert this now.. before it goes live.. and I have time, so it can handle
the activity. I am just not sure if it will be too complex to change it at
this stage.
> would I use the existing application to now connect to SQL. Is this
> difficult?
http://www.able-consulting.com/ADO_Conn.htm-- connections
You will have to modify some code like DELETION from Table
In access we write DELETE * FROM Table as opposite in T_SQL DELETE FROM
Table.
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:814EAE75-4FDE-4053-9B43-47C908C888F1@.microsoft.com...
> I currently have a database in Access 2000 that I wish to upsize to Sql
2000.
> I have read about the upsize wizard. This sounds ideal. However, I have a
> company intranet application developed based on the Access database. How
> would I use the existing application to now connect to SQL. Is this
> difficult? The intranet is still in its initial stages...and I have read
that
> sql would be better. We have Small Business Server 2003 so it comes with
the
> system. Is there a web site/page that might help me convert this website
and
> how to create a connection. I thought perhaps it would be best to try and
> convert this now.. before it goes live.. and I have time, so it can handle
> the activity. I am just not sure if it will be too complex to change it at
> this stage.
>
I have read about the upsize wizard. This sounds ideal. However, I have a
company intranet application developed based on the Access database. How
would I use the existing application to now connect to SQL. Is this
difficult? The intranet is still in its initial stages...and I have read that
sql would be better. We have Small Business Server 2003 so it comes with the
system. Is there a web site/page that might help me convert this website and
how to create a connection. I thought perhaps it would be best to try and
convert this now.. before it goes live.. and I have time, so it can handle
the activity. I am just not sure if it will be too complex to change it at
this stage.
> would I use the existing application to now connect to SQL. Is this
> difficult?
http://www.able-consulting.com/ADO_Conn.htm-- connections
You will have to modify some code like DELETION from Table
In access we write DELETE * FROM Table as opposite in T_SQL DELETE FROM
Table.
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:814EAE75-4FDE-4053-9B43-47C908C888F1@.microsoft.com...
> I currently have a database in Access 2000 that I wish to upsize to Sql
2000.
> I have read about the upsize wizard. This sounds ideal. However, I have a
> company intranet application developed based on the Access database. How
> would I use the existing application to now connect to SQL. Is this
> difficult? The intranet is still in its initial stages...and I have read
that
> sql would be better. We have Small Business Server 2003 so it comes with
the
> system. Is there a web site/page that might help me convert this website
and
> how to create a connection. I thought perhaps it would be best to try and
> convert this now.. before it goes live.. and I have time, so it can handle
> the activity. I am just not sure if it will be too complex to change it at
> this stage.
>
Frontpage and upsized db from Access to SQL 2000-difficult?
I currently have a database in Access 2000 that I wish to upsize to Sql 2000.
I have read about the upsize wizard. This sounds ideal. However, I have a
company intranet application developed based on the Access database. How
would I use the existing application to now connect to SQL. Is this
difficult? The intranet is still in its initial stages...and I have read that
sql would be better. We have Small Business Server 2003 so it comes with the
system. Is there a web site/page that might help me convert this website and
how to create a connection. I thought perhaps it would be best to try and
convert this now.. before it goes live.. and I have time, so it can handle
the activity. I am just not sure if it will be too complex to change it at
this stage.> would I use the existing application to now connect to SQL. Is this
> difficult?
http://www.able-consulting.com/ADO_Conn.htm-- connections
You will have to modify some code like DELETION from Table
In access we write DELETE * FROM Table as opposite in T_SQL DELETE FROM
Table.
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:814EAE75-4FDE-4053-9B43-47C908C888F1@.microsoft.com...
> I currently have a database in Access 2000 that I wish to upsize to Sql
2000.
> I have read about the upsize wizard. This sounds ideal. However, I have a
> company intranet application developed based on the Access database. How
> would I use the existing application to now connect to SQL. Is this
> difficult? The intranet is still in its initial stages...and I have read
that
> sql would be better. We have Small Business Server 2003 so it comes with
the
> system. Is there a web site/page that might help me convert this website
and
> how to create a connection. I thought perhaps it would be best to try and
> convert this now.. before it goes live.. and I have time, so it can handle
> the activity. I am just not sure if it will be too complex to change it at
> this stage.
>
I have read about the upsize wizard. This sounds ideal. However, I have a
company intranet application developed based on the Access database. How
would I use the existing application to now connect to SQL. Is this
difficult? The intranet is still in its initial stages...and I have read that
sql would be better. We have Small Business Server 2003 so it comes with the
system. Is there a web site/page that might help me convert this website and
how to create a connection. I thought perhaps it would be best to try and
convert this now.. before it goes live.. and I have time, so it can handle
the activity. I am just not sure if it will be too complex to change it at
this stage.> would I use the existing application to now connect to SQL. Is this
> difficult?
http://www.able-consulting.com/ADO_Conn.htm-- connections
You will have to modify some code like DELETION from Table
In access we write DELETE * FROM Table as opposite in T_SQL DELETE FROM
Table.
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:814EAE75-4FDE-4053-9B43-47C908C888F1@.microsoft.com...
> I currently have a database in Access 2000 that I wish to upsize to Sql
2000.
> I have read about the upsize wizard. This sounds ideal. However, I have a
> company intranet application developed based on the Access database. How
> would I use the existing application to now connect to SQL. Is this
> difficult? The intranet is still in its initial stages...and I have read
that
> sql would be better. We have Small Business Server 2003 so it comes with
the
> system. Is there a web site/page that might help me convert this website
and
> how to create a connection. I thought perhaps it would be best to try and
> convert this now.. before it goes live.. and I have time, so it can handle
> the activity. I am just not sure if it will be too complex to change it at
> this stage.
>
Frontpage and upsized db from Access to SQL 2000-difficult?
I currently have a database in Access 2000 that I wish to upsize to Sql 2000
.
I have read about the upsize wizard. This sounds ideal. However, I have a
company intranet application developed based on the Access database. How
would I use the existing application to now connect to SQL. Is this
difficult? The intranet is still in its initial stages...and I have read tha
t
sql would be better. We have Small Business Server 2003 so it comes with the
system. Is there a web site/page that might help me convert this website an
d
how to create a connection. I thought perhaps it would be best to try and
convert this now.. before it goes live.. and I have time, so it can handle
the activity. I am just not sure if it will be too complex to change it at
this stage.> would I use the existing application to now connect to SQL. Is this
> difficult?
http://www.able-consulting.com/ADO_Conn.htm-- connections
You will have to modify some code like DELETION from Table
In access we write DELETE * FROM Table as opposite in T_SQL DELETE FROM
Table.
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:814EAE75-4FDE-4053-9B43-47C908C888F1@.microsoft.com...
> I currently have a database in Access 2000 that I wish to upsize to Sql
2000.
> I have read about the upsize wizard. This sounds ideal. However, I have a
> company intranet application developed based on the Access database. How
> would I use the existing application to now connect to SQL. Is this
> difficult? The intranet is still in its initial stages...and I have read
that
> sql would be better. We have Small Business Server 2003 so it comes with
the
> system. Is there a web site/page that might help me convert this website
and
> how to create a connection. I thought perhaps it would be best to try and
> convert this now.. before it goes live.. and I have time, so it can handle
> the activity. I am just not sure if it will be too complex to change it at
> this stage.
>
.
I have read about the upsize wizard. This sounds ideal. However, I have a
company intranet application developed based on the Access database. How
would I use the existing application to now connect to SQL. Is this
difficult? The intranet is still in its initial stages...and I have read tha
t
sql would be better. We have Small Business Server 2003 so it comes with the
system. Is there a web site/page that might help me convert this website an
d
how to create a connection. I thought perhaps it would be best to try and
convert this now.. before it goes live.. and I have time, so it can handle
the activity. I am just not sure if it will be too complex to change it at
this stage.> would I use the existing application to now connect to SQL. Is this
> difficult?
http://www.able-consulting.com/ADO_Conn.htm-- connections
You will have to modify some code like DELETION from Table
In access we write DELETE * FROM Table as opposite in T_SQL DELETE FROM
Table.
"Cheryl" <Cheryl@.discussions.microsoft.com> wrote in message
news:814EAE75-4FDE-4053-9B43-47C908C888F1@.microsoft.com...
> I currently have a database in Access 2000 that I wish to upsize to Sql
2000.
> I have read about the upsize wizard. This sounds ideal. However, I have a
> company intranet application developed based on the Access database. How
> would I use the existing application to now connect to SQL. Is this
> difficult? The intranet is still in its initial stages...and I have read
that
> sql would be better. We have Small Business Server 2003 so it comes with
the
> system. Is there a web site/page that might help me convert this website
and
> how to create a connection. I thought perhaps it would be best to try and
> convert this now.. before it goes live.. and I have time, so it can handle
> the activity. I am just not sure if it will be too complex to change it at
> this stage.
>
Wednesday, March 21, 2012
Front-end tools -- Which is the most productive?
After having seen my co-worker reinventing the wheel
when he busily labored to build MS Access framework, I want to share
my perspective.
when he busily labored to build MS Access framework, I want to share
my perspective.
Having experienced with Access, Visual Basic, Visual C++,
and PowerBuilder, I think Sybase's PowerBuilder is the most
productive tool to build front-ends for any database or
client/server applications. PowerBuilder's datawindow
is very powerful.
Binh
http://vmdd.tech.mylinuxisp.com/catalog/I agree, and it does way more than client-server too. But the market mind
share isn't with Sybase - so the herd goes down the wrong path.
Unfortunately a lot of executive decisions are made by taking in the
powerpoint market pitch, and not through anything that resembles critical
rational thinking.
Essay on the evils of PowerPoint.= http://www.edwardtufte.com/tufte/books_pp
"http://vmdd.tech.mylinuxisp.com/catalog/" <binhph@.gmail.com> wrote in
message news:bb3470aa.0409222052.3488d043@.posting.google.c om...
> After having seen my co-worker reinventing the wheel
> when he busily labored to build MS Access framework, I want to share
> my perspective.
> Having experienced with Access, Visual Basic, Visual C++,
> and PowerBuilder, I think Sybase's PowerBuilder is the most
> productive tool to build front-ends for any database or
> client/server applications. PowerBuilder's datawindow
> is very powerful.
> Binh
> http://vmdd.tech.mylinuxisp.com/catalog/|||Hey:
You know I have worked with several products, nothing to beat Web
based front end using ASP/ASP.NET with Oracle/SQL Server back-end. No
client maintenance, just a browser and a NIC. What else can you ask
for ?
Thanks, GIrish
front/backend access application--conversion to MSSQL--advice
I have an application that uses Acces as a backend and VBA as front end. Application is secured and is supplied on a CD with setup.exe.
Can I use VB 2005 and MS SQL to achieve the same?
Would I be able to package my application with all the neccessery files (assuming that client does not have any e.g. SQL server) so that multiple front ends can access data from common source?
Would I be able to secure such an application using only VS 2005?
What would I need to quickly learn how to achieve the above ( any books you can suggest maybe)?
You can absolutely use SQL Server Express to ship as part of your application - it is designed for that. You can find a whitepaper with guidance on this at http://msdn.microsoft.com/sql/express/default.aspx?pull=/library/en-us/dnsse/html/emsqlexcustapp.asp. The whitepaper includes an explanation of how you can use a feature called ClickOnce in Visual Studio/.NET to deploy your client applications. You should also sign up for redistribution rights for Express at http://www.microsoft.com/sql/editions/express/redistregister.mspx.
Thanks< MJ
Front End options
I need people's expertise on this. I'm currently at a
crossroad with my Access XP dbs. We're planning on moving
our access tables to SQL 2k. My boss wants me to look
into options for the Front End. The dbs are mission
critical (worked on 24/7) and would like to be more
flexible in the future to incorporate other things/info.
Currently I have an Access XP front end. I was wondering
what would be the best front end to use with SQL?
Here is what I found out so far and I'm not sure if my
findings are even accurate.
1. Access ADP - more efficient than mdb since it doesn't
use the jet engine. Less work because I don't have to
remake all the forms/reports/etc... I don't know too much
of the advantages of ADP.
2. Webpage - faster in speed than Access. I already have
several pages that access the sql server. A lil more of a
learning curve because I would have to get into
CSS/frames/javascripts because my current db has lots of
forms, subforms, reports and subreports to convert over.
3. C++ or C# - someone mentioned it was the way to go in
the future. But I don't have any knowledge in that and it
would be a big learning curve and maybe not for this big
of a project.
4. VB - speeds faster but more work than Access.
Learning curve would be a lil much too.
Anyone can give their input to help me make a decision on
which way to go?
Thanks.
Ngan
I can't really help you choose because I don't know enough about your
application, but I will point out a few things with your numbered list
below:
1. Not true. an mdb can be just as efficient as an adp, and you would
have to redo forms and reports because you'd probably have to redo the
underlying queries. You give up the flexibility of local storage for
static data and heterogeneous joins. Regardless of mdb or adp, you'll
need to redo the front end app to fetch less data and rewrite most of
your saved queries as stored procedures/views.
2. ASP.NET is a good choice if it's a web app. Forget about easy
subforms/subreports for any web FE you might choose. Only Access does
subforms well.
3. If you go the .NET route, you don't need to learn C#, much less
C++. VB.NET is just as good and the learning curve won't be so high
for you. However, Windows forms for database apps don't have all of
the features you like in Access (subforms again), and working with
data is totally alien to the Access way of doing things.
4. VB6 would be a step back, more work, no real advantage unless you
factor in ease of deployment. You'll still need to rewrite those
queries. No subforms.
My recommendation would be to redo your Access mdb FE to be more
efficient against a SQL Server BE by fetching less data and using
stored procedures for reports, etc. You can cache static data for
combo boxes and dynamically load subform data in local tables.
Focusing on fixing whatever is wrong with your Access mdb in terms of
table and application design to make it more efficient when you
migrate the data to SQL Server will be most productive use of your
time. SQL Server has a very high learning curve, and you'd be better
off mastering SQLS first rather than trying to do that at the same
time as learning another programming language or FE application.
--Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
On Tue, 10 Aug 2004 13:19:38 -0700, "Ngan"
<anonymous@.discussions.microsoft.com> wrote:
>I need people's expertise on this. I'm currently at a
>crossroad with my Access XP dbs. We're planning on moving
>our access tables to SQL 2k. My boss wants me to look
>into options for the Front End. The dbs are mission
>critical (worked on 24/7) and would like to be more
>flexible in the future to incorporate other things/info.
>Currently I have an Access XP front end. I was wondering
>what would be the best front end to use with SQL?
>Here is what I found out so far and I'm not sure if my
>findings are even accurate.
>1. Access ADP - more efficient than mdb since it doesn't
>use the jet engine. Less work because I don't have to
>remake all the forms/reports/etc... I don't know too much
>of the advantages of ADP.
>2. Webpage - faster in speed than Access. I already have
>several pages that access the sql server. A lil more of a
>learning curve because I would have to get into
>CSS/frames/javascripts because my current db has lots of
>forms, subforms, reports and subreports to convert over.
>3. C++ or C# - someone mentioned it was the way to go in
>the future. But I don't have any knowledge in that and it
>would be a big learning curve and maybe not for this big
>of a project.
>4. VB - speeds faster but more work than Access.
>Learning curve would be a lil much too.
>Anyone can give their input to help me make a decision on
>which way to go?
>Thanks.
>Ngan
|||Thanks Mary for your insight. I actually bought your
book
1. Does a mdb FE work well regardless of how many tables
there are and how many records in those tables? I
currently have about 40 tables and the tables that most
people write to have over 100,000 records each.
2. What about the number of concurrent users using the
mdb FE with the SQL BE? Currently with my access dbs,
once in awhile I get record corruption (mostly because of
the memo fields). I may have up to 50 concurrent users
(reading data and/or writing data).
If mdb works as well as any FE app and I work on fixing
the bottleneck, can it hold up to the number of users and
records?
Thanks!
Ngan
>--Original Message--
>I can't really help you choose because I don't know
enough about your
>application, but I will point out a few things with your
numbered list
>below:
>1. Not true. an mdb can be just as efficient as an adp,
and you would
>have to redo forms and reports because you'd probably
have to redo the
>underlying queries. You give up the flexibility of local
storage for
>static data and heterogeneous joins. Regardless of mdb or
adp, you'll
>need to redo the front end app to fetch less data and
rewrite most of
>your saved queries as stored procedures/views.
>2. ASP.NET is a good choice if it's a web app. Forget
about easy
>subforms/subreports for any web FE you might choose. Only
Access does
>subforms well.
>3. If you go the .NET route, you don't need to learn C#,
much less
>C++. VB.NET is just as good and the learning curve won't
be so high
>for you. However, Windows forms for database apps don't
have all of
>the features you like in Access (subforms again), and
working with
>data is totally alien to the Access way of doing things.
>4. VB6 would be a step back, more work, no real advantage
unless you
>factor in ease of deployment. You'll still need to
rewrite those
>queries. No subforms.
>My recommendation would be to redo your Access mdb FE to
be more
>efficient against a SQL Server BE by fetching less data
and using
>stored procedures for reports, etc. You can cache static
data for
>combo boxes and dynamically load subform data in local
tables.
>Focusing on fixing whatever is wrong with your Access mdb
in terms of
>table and application design to make it more efficient
when you
>migrate the data to SQL Server will be most productive
use of your
>time. SQL Server has a very high learning curve, and
you'd be better
>off mastering SQLS first rather than trying to do that at
the same
>time as learning another programming language or FE
application.[vbcol=seagreen]
>--Mary
>Microsoft Access Developer's Guide to SQL Server
>http://www.amazon.com/exec/obidos/ASIN/0672319446
>On Tue, 10 Aug 2004 13:19:38 -0700, "Ngan"
><anonymous@.discussions.microsoft.com> wrote:
moving[vbcol=seagreen]
wondering[vbcol=seagreen]
doesn't[vbcol=seagreen]
much[vbcol=seagreen]
have[vbcol=seagreen]
a[vbcol=seagreen]
in[vbcol=seagreen]
it[vbcol=seagreen]
on
>.
>
|||1 -- As long as you don't link to the entire table or try to bind
forms to an entire table. Create a query-by-form UI so that users must
select only a single record to edit data. Use Jet for storing lookup
tables and subform data.
2 -- 50 concurrent users editing data is absolutely not a problem for
SQL Server if you follow my recommendations in (1). If you've been
supporting that many in Access then your table design is probably
sound in the sense that you've eliminated concurrency conflicts by
ensuring that users never (or rarely) edit the same row at the same
time.
Since you already bought the book, look up the chapter on creating
unbound applications. The idea there is that you have a lightweight
front end, fetch minimal data read-only and post changes in Update and
Insert statements. You also have to handle concurrency issues in your
code, but you can just *borrow* the code we've already written. It
very much mimics the way a web application works. Using that
technique, you could easily support hundreds of concurrent users.
--Mary
On Wed, 11 Aug 2004 08:41:58 -0700, "Ngan"
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks Mary for your insight. I actually bought your
>book
>1. Does a mdb FE work well regardless of how many tables
>there are and how many records in those tables? I
>currently have about 40 tables and the tables that most
>people write to have over 100,000 records each.
>2. What about the number of concurrent users using the
>mdb FE with the SQL BE? Currently with my access dbs,
>once in awhile I get record corruption (mostly because of
>the memo fields). I may have up to 50 concurrent users
>(reading data and/or writing data).
>If mdb works as well as any FE app and I work on fixing
>the bottleneck, can it hold up to the number of users and
>records?
>Thanks!
>Ngan
>
>enough about your
>numbered list
>and you would
>have to redo the
>storage for
>adp, you'll
>rewrite most of
>about easy
>Access does
>much less
>be so high
>have all of
>working with
>unless you
>rewrite those
>be more
>and using
>data for
>tables.
>in terms of
>when you
>use of your
>you'd be better
>the same
>application.
>moving
>wondering
>doesn't
>much
>have
>a
>in
>it
>on
sql
crossroad with my Access XP dbs. We're planning on moving
our access tables to SQL 2k. My boss wants me to look
into options for the Front End. The dbs are mission
critical (worked on 24/7) and would like to be more
flexible in the future to incorporate other things/info.
Currently I have an Access XP front end. I was wondering
what would be the best front end to use with SQL?
Here is what I found out so far and I'm not sure if my
findings are even accurate.
1. Access ADP - more efficient than mdb since it doesn't
use the jet engine. Less work because I don't have to
remake all the forms/reports/etc... I don't know too much
of the advantages of ADP.
2. Webpage - faster in speed than Access. I already have
several pages that access the sql server. A lil more of a
learning curve because I would have to get into
CSS/frames/javascripts because my current db has lots of
forms, subforms, reports and subreports to convert over.
3. C++ or C# - someone mentioned it was the way to go in
the future. But I don't have any knowledge in that and it
would be a big learning curve and maybe not for this big
of a project.
4. VB - speeds faster but more work than Access.
Learning curve would be a lil much too.
Anyone can give their input to help me make a decision on
which way to go?
Thanks.
Ngan
I can't really help you choose because I don't know enough about your
application, but I will point out a few things with your numbered list
below:
1. Not true. an mdb can be just as efficient as an adp, and you would
have to redo forms and reports because you'd probably have to redo the
underlying queries. You give up the flexibility of local storage for
static data and heterogeneous joins. Regardless of mdb or adp, you'll
need to redo the front end app to fetch less data and rewrite most of
your saved queries as stored procedures/views.
2. ASP.NET is a good choice if it's a web app. Forget about easy
subforms/subreports for any web FE you might choose. Only Access does
subforms well.
3. If you go the .NET route, you don't need to learn C#, much less
C++. VB.NET is just as good and the learning curve won't be so high
for you. However, Windows forms for database apps don't have all of
the features you like in Access (subforms again), and working with
data is totally alien to the Access way of doing things.
4. VB6 would be a step back, more work, no real advantage unless you
factor in ease of deployment. You'll still need to rewrite those
queries. No subforms.
My recommendation would be to redo your Access mdb FE to be more
efficient against a SQL Server BE by fetching less data and using
stored procedures for reports, etc. You can cache static data for
combo boxes and dynamically load subform data in local tables.
Focusing on fixing whatever is wrong with your Access mdb in terms of
table and application design to make it more efficient when you
migrate the data to SQL Server will be most productive use of your
time. SQL Server has a very high learning curve, and you'd be better
off mastering SQLS first rather than trying to do that at the same
time as learning another programming language or FE application.
--Mary
Microsoft Access Developer's Guide to SQL Server
http://www.amazon.com/exec/obidos/ASIN/0672319446
On Tue, 10 Aug 2004 13:19:38 -0700, "Ngan"
<anonymous@.discussions.microsoft.com> wrote:
>I need people's expertise on this. I'm currently at a
>crossroad with my Access XP dbs. We're planning on moving
>our access tables to SQL 2k. My boss wants me to look
>into options for the Front End. The dbs are mission
>critical (worked on 24/7) and would like to be more
>flexible in the future to incorporate other things/info.
>Currently I have an Access XP front end. I was wondering
>what would be the best front end to use with SQL?
>Here is what I found out so far and I'm not sure if my
>findings are even accurate.
>1. Access ADP - more efficient than mdb since it doesn't
>use the jet engine. Less work because I don't have to
>remake all the forms/reports/etc... I don't know too much
>of the advantages of ADP.
>2. Webpage - faster in speed than Access. I already have
>several pages that access the sql server. A lil more of a
>learning curve because I would have to get into
>CSS/frames/javascripts because my current db has lots of
>forms, subforms, reports and subreports to convert over.
>3. C++ or C# - someone mentioned it was the way to go in
>the future. But I don't have any knowledge in that and it
>would be a big learning curve and maybe not for this big
>of a project.
>4. VB - speeds faster but more work than Access.
>Learning curve would be a lil much too.
>Anyone can give their input to help me make a decision on
>which way to go?
>Thanks.
>Ngan
|||Thanks Mary for your insight. I actually bought your
book
1. Does a mdb FE work well regardless of how many tables
there are and how many records in those tables? I
currently have about 40 tables and the tables that most
people write to have over 100,000 records each.
2. What about the number of concurrent users using the
mdb FE with the SQL BE? Currently with my access dbs,
once in awhile I get record corruption (mostly because of
the memo fields). I may have up to 50 concurrent users
(reading data and/or writing data).
If mdb works as well as any FE app and I work on fixing
the bottleneck, can it hold up to the number of users and
records?
Thanks!
Ngan
>--Original Message--
>I can't really help you choose because I don't know
enough about your
>application, but I will point out a few things with your
numbered list
>below:
>1. Not true. an mdb can be just as efficient as an adp,
and you would
>have to redo forms and reports because you'd probably
have to redo the
>underlying queries. You give up the flexibility of local
storage for
>static data and heterogeneous joins. Regardless of mdb or
adp, you'll
>need to redo the front end app to fetch less data and
rewrite most of
>your saved queries as stored procedures/views.
>2. ASP.NET is a good choice if it's a web app. Forget
about easy
>subforms/subreports for any web FE you might choose. Only
Access does
>subforms well.
>3. If you go the .NET route, you don't need to learn C#,
much less
>C++. VB.NET is just as good and the learning curve won't
be so high
>for you. However, Windows forms for database apps don't
have all of
>the features you like in Access (subforms again), and
working with
>data is totally alien to the Access way of doing things.
>4. VB6 would be a step back, more work, no real advantage
unless you
>factor in ease of deployment. You'll still need to
rewrite those
>queries. No subforms.
>My recommendation would be to redo your Access mdb FE to
be more
>efficient against a SQL Server BE by fetching less data
and using
>stored procedures for reports, etc. You can cache static
data for
>combo boxes and dynamically load subform data in local
tables.
>Focusing on fixing whatever is wrong with your Access mdb
in terms of
>table and application design to make it more efficient
when you
>migrate the data to SQL Server will be most productive
use of your
>time. SQL Server has a very high learning curve, and
you'd be better
>off mastering SQLS first rather than trying to do that at
the same
>time as learning another programming language or FE
application.[vbcol=seagreen]
>--Mary
>Microsoft Access Developer's Guide to SQL Server
>http://www.amazon.com/exec/obidos/ASIN/0672319446
>On Tue, 10 Aug 2004 13:19:38 -0700, "Ngan"
><anonymous@.discussions.microsoft.com> wrote:
moving[vbcol=seagreen]
wondering[vbcol=seagreen]
doesn't[vbcol=seagreen]
much[vbcol=seagreen]
have[vbcol=seagreen]
a[vbcol=seagreen]
in[vbcol=seagreen]
it[vbcol=seagreen]
on
>.
>
|||1 -- As long as you don't link to the entire table or try to bind
forms to an entire table. Create a query-by-form UI so that users must
select only a single record to edit data. Use Jet for storing lookup
tables and subform data.
2 -- 50 concurrent users editing data is absolutely not a problem for
SQL Server if you follow my recommendations in (1). If you've been
supporting that many in Access then your table design is probably
sound in the sense that you've eliminated concurrency conflicts by
ensuring that users never (or rarely) edit the same row at the same
time.
Since you already bought the book, look up the chapter on creating
unbound applications. The idea there is that you have a lightweight
front end, fetch minimal data read-only and post changes in Update and
Insert statements. You also have to handle concurrency issues in your
code, but you can just *borrow* the code we've already written. It
very much mimics the way a web application works. Using that
technique, you could easily support hundreds of concurrent users.
--Mary
On Wed, 11 Aug 2004 08:41:58 -0700, "Ngan"
<anonymous@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Thanks Mary for your insight. I actually bought your
>book
>1. Does a mdb FE work well regardless of how many tables
>there are and how many records in those tables? I
>currently have about 40 tables and the tables that most
>people write to have over 100,000 records each.
>2. What about the number of concurrent users using the
>mdb FE with the SQL BE? Currently with my access dbs,
>once in awhile I get record corruption (mostly because of
>the memo fields). I may have up to 50 concurrent users
>(reading data and/or writing data).
>If mdb works as well as any FE app and I work on fixing
>the bottleneck, can it hold up to the number of users and
>records?
>Thanks!
>Ngan
>
>enough about your
>numbered list
>and you would
>have to redo the
>storage for
>adp, you'll
>rewrite most of
>about easy
>Access does
>much less
>be so high
>have all of
>working with
>unless you
>rewrite those
>be more
>and using
>data for
>tables.
>in terms of
>when you
>use of your
>you'd be better
>the same
>application.
>moving
>wondering
>doesn't
>much
>have
>a
>in
>it
>on
sql
Front End Access and Back End as SQL Server
Dear Friends,
We have MS Access database with Forms and Reports, which was started 10 years ago by users and now the data is growing very rapidly.
Did anyone tried by having MS Access as front end and SQL Server 2000/2005 as backend with minimum modifications to the forms and reports in MS Access?
Please let me know, your ideas and if there are any links in the web or in Microsoft please provide here.
Thanks in advance,
Wrong forum for this - you might try the Database Engine forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=93&SiteID=1)or the Getting Started forum (http://forums.microsoft.com/MSDN/ShowForum.aspx?ForumID=158&SiteID=1)
From SQL SERVER TO MSDE
i have an access application based on sql server
now i was told that for small offices msde is enough and chiper
if it is so can somebody tell me
how to convert the database from sql to msde?
and it cost a lot of code working?
thanks ahead
sam
hi Sam,
Sam wrote:
> i have an access application based on sql server
> now i was told that for small offices msde is enough and chiper
> if it is so can somebody tell me
> how to convert the database from sql to msde?
> and it cost a lot of code working?
MSDE has some constraints built in it, but it is the very same engine as SQL
Server is... so you do not have to worry about "converting" SQL Server
databases into MSDE databases as they are the same...
MSDE has a limit on the file size it's databases data file(s) can reach,
that's to say 2gb per database data files...
other limits are about missing feature, like Full Text indexes, olap
features, partial replication, and so on... but as long as you "stay" into
the architectural limits and your applications do not cover missing features
you will be ok.. further info at
http://www.microsoft.com/sql/msde/pr...o/default.mspx
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
now i was told that for small offices msde is enough and chiper
if it is so can somebody tell me
how to convert the database from sql to msde?
and it cost a lot of code working?
thanks ahead
sam
hi Sam,
Sam wrote:
> i have an access application based on sql server
> now i was told that for small offices msde is enough and chiper
> if it is so can somebody tell me
> how to convert the database from sql to msde?
> and it cost a lot of code working?
MSDE has some constraints built in it, but it is the very same engine as SQL
Server is... so you do not have to worry about "converting" SQL Server
databases into MSDE databases as they are the same...
MSDE has a limit on the file size it's databases data file(s) can reach,
that's to say 2gb per database data files...
other limits are about missing feature, like Full Text indexes, olap
features, partial replication, and so on... but as long as you "stay" into
the architectural limits and your applications do not cover missing features
you will be ok.. further info at
http://www.microsoft.com/sql/msde/pr...o/default.mspx
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Monday, March 19, 2012
from client how to access remote stored procedures
hai all
can any one give syntax in sql server like
how to access remote stored procedures ?
wheather we have to set any permissions in client machine to access the
remote stored procedure
please give solution (sytax or procedure ) how to access from sqlserver
Thanks & Regards
SVG SRINIVASThat depends on your coding language, what are you using ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"S V G Srinivas" <svgsrinivas@.dev.visualsoft-tech.com> schrieb im
Newsbeitrag news:uqm50%23zZFHA.2796@.TK2MSFTNGP10.phx.gbl...
> hai all
> can any one give syntax in sql server like
> how to access remote stored procedures ?
> wheather we have to set any permissions in client machine to access
> the
> remote stored procedure
> please give solution (sytax or procedure ) how to access from sqlserver
> Thanks & Regards
> SVG SRINIVAS
>|||Hi
Check out the topics "How to set up a linked server", "Configuring Linked
Servers" and "Distributed Queries" and "Accessing External Data" in Books
Online.
John
"S V G Srinivas" <svgsrinivas@.dev.visualsoft-tech.com> wrote in message
news:uqm50%23zZFHA.2796@.TK2MSFTNGP10.phx.gbl...
> hai all
> can any one give syntax in sql server like
> how to access remote stored procedures ?
> wheather we have to set any permissions in client machine to access
> the
> remote stored procedure
> please give solution (sytax or procedure ) how to access from sqlserver
> Thanks & Regards
> SVG SRINIVAS
>
can any one give syntax in sql server like
how to access remote stored procedures ?
wheather we have to set any permissions in client machine to access the
remote stored procedure
please give solution (sytax or procedure ) how to access from sqlserver
Thanks & Regards
SVG SRINIVASThat depends on your coding language, what are you using ?
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--
"S V G Srinivas" <svgsrinivas@.dev.visualsoft-tech.com> schrieb im
Newsbeitrag news:uqm50%23zZFHA.2796@.TK2MSFTNGP10.phx.gbl...
> hai all
> can any one give syntax in sql server like
> how to access remote stored procedures ?
> wheather we have to set any permissions in client machine to access
> the
> remote stored procedure
> please give solution (sytax or procedure ) how to access from sqlserver
> Thanks & Regards
> SVG SRINIVAS
>|||Hi
Check out the topics "How to set up a linked server", "Configuring Linked
Servers" and "Distributed Queries" and "Accessing External Data" in Books
Online.
John
"S V G Srinivas" <svgsrinivas@.dev.visualsoft-tech.com> wrote in message
news:uqm50%23zZFHA.2796@.TK2MSFTNGP10.phx.gbl...
> hai all
> can any one give syntax in sql server like
> how to access remote stored procedures ?
> wheather we have to set any permissions in client machine to access
> the
> remote stored procedure
> please give solution (sytax or procedure ) how to access from sqlserver
> Thanks & Regards
> SVG SRINIVAS
>
from asp classic & asp.net to Access database changing to sql server
Hello,We are re-writing our site in asp.net using sql server. Most of the site uses asp classic and it was to an access database. During the conversion we have everything working correct to SQL Server except for the asp.net connection string. There is an important part of the application using asp.net which works fine with our connection string to the access database. To recap our problem is the connection string from asp.net to sql server.
This code works fine for the asp.net to access in the web.cnfg file
</microsoft.web>
<connectionStrings>
<add name="SalesConnectionString" connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=E:\inetpub\vhosts\themarketingvp.com\subdomains\vp\httpdocs\fpdb\salesMain.mdb" providerName="System.Data.OleDb"/>
<add name="ODBCSalesConnectionString" connectionString="DRIVER={Microsoft Access Driver (*.mdb)};DBQ=URL=E:\inetpub\vhosts\themarketingvp.com\subdomains\vp\httpdocs\fpdb\salesMain.mdb"/>
<add name="RawConnectionString" connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=E:\inetpub\vhosts\themarketingvp.com\subdomains\vp\httpdocs\fpdb\salesMain.mdb" providerName="System.Data.OleDb"/>
<add name="ConnectionString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\inventoryStatus.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True" providerName="System.Data.SqlClient"/>
</connectionStrings>
<system.web
The code in the global.asa which works fine for classic asp to sql server also works fine and is as follows
'--Project Data Connection
Application("sales_ConnectionString") = "Driver={SQL Native Client};Server=DMSERVER01;Database=SQLsalesMain;UID=nTrack;PWD=nTrack2k3"
Application("sales_ConnectionTimeout") = 15
Application("sales_CommandTimeout") = 30
Application("sales_CursorLocation") = 3
Application("sales_RuntimeUserName") = ""
Application("sales_RuntimePassword") = ""
Our programmer who set this up is out for a couple of weeks and I would appreciate any help in the correct connection string from asp.net to the sql server database in the web.cnfg file
Thanks
<add name="ConnectionString" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\inventoryStatus.mdf;Integrated Security=True;Connect Timeout=30;User Instance=True" providerName="System.Data.SqlClient"/>
</connectionStrings>
<system.web>
The above is your problem and your developer not knowing the meaning of User instance because it is for development only database unless you plan to deploy in Express the reason there is no such thing as User instance in full edition SQL Server so read the content of the MSDN link carefully or your code will not run. The text below is from the MSDN link. Hope this helps.
(SQL Server Express Edition allows only a single connection to an .mdf file when you connect with a connection string that has User Instance set to true.)
http://msdn2.microsoft.com/en-us/library/ms228037.aspx
http://www.connectionstrings.com/?carrier=sqlserver2005
<add name="SalesConnectionString" connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=E:\inetpub\vhosts\themarketingvp.com\subdomains\vp\httpdocs\fpdb\salesMain.mdb" providerName="System.Data.OleDb"/>
The above is the connection we are talking about.
Thanks...
|||That is not a SQL Server connection string that is the reason I gave you the link to the connection string site. Hope this helps.|||Thanks,
I know that is not a SQL Server connection string. I was asking for help based on the way the salesMain connection string for SQL in the posted. I have how asp classic connects to SQL, which works fine and was asking how to get it to work with asp.net. I have both connection strings shown in the code in the first post.
Dave
|||<add name="SalesConnectionString" connectionString="Provider=Microsoft.Jet.OLEDB.4.0;Data Source=E:\inetpub\vhosts\themarketingvp.com\subdomains\vp\httpdocs\fpdb\salesMain.mdb" providerName="System.Data.OleDb"/>
<connectionStrings>
<add name="salesMain" connectionString="Server=(local);Integrated Security=True;Database=salesMain;"
providerName="System.Data.SqlClient" />
</connectionStrings>
I have started the correct connection string but you have to add your server name to get it right because you cannot put SQL Server database in inetpub in a network drive because SQL Server decides where the database goes and it is the location below. What I mean is in RDBMS(relational database management systems) the server controls where the database goes. You still have to correct the previous connection string I pointed out to you because again there is no user instance in full SQL Server. You or your developer have to spend time to know connection strings and SQL Server permissions or your application will not run. Hope this helps.
C:\Program Files\Microsoft SQL Server\MSSQL\DATA
http://forums.asp.net/thread/1491403.aspx
Monday, March 12, 2012
from access to sql
hope you can help.
I need to get my access db backend to sql. I have tried the upsizing
wizard but the get message "overflow" and cannot get any further.
I also use queries that reference two date ranges from forms such as
BETWEEN forms!form1!text1 AND forms!form1!text2. How can i achieve
this in an sql view?You will need lots of advice. I suggest that you buy "Microsoft Access
Developer's Guide to SQL Server". It's awesome and will answer all your
questions, and save you countless hours of frustration.
--
Jerry Boone
Analytical Technologies, Inc.
http://www.antech.biz
"Mark" <maworrell@.ananzi.co.za> wrote in message
news:ddbf09eb.0310231219.20065b09@.posting.google.c om...
> hope you can help.
> I need to get my access db backend to sql. I have tried the upsizing
> wizard but the get message "overflow" and cannot get any further.
> I also use queries that reference two date ranges from forms such as
> BETWEEN forms!form1!text1 AND forms!form1!text2. How can i achieve
> this in an sql view?|||One option for you. Just a thought. We use Borland Delphi as the main
language at work. It comes with an upsizing tool called 'Data Pump'
which is really useful for taking data from one db to another. I use
this quite a bit for Access -> SQL transfers. It may be worthwhile
doing a few searches on the Internet for this to see if Borland or
anyone else can help with a similar tool. We get it bundled with
Delphi (I think it's available with Paradox as well), but it may be
available as a seperate tool.
The problem you will have is with getting the structure copied over to
SQL. If you can find a way of creating the correct table structure in
the SQL db, then you can easily link the table through ODBC into
Access and import the data through a query. Problem is the structure
has to be there already.
If you only have a few tables and they aren't too big, I'd look at
creating them by hand on SQL instead of spending time looking for ways
to move the data. Moving the data is the easy bit.
"Jerry Boone" <jerry@.antech.biz.nospam> wrote in message news:<Z7rub.1119$LL3.330@.newssvr23.news.prodigy.com>...
> You will need lots of advice. I suggest that you buy "Microsoft Access
> Developer's Guide to SQL Server". It's awesome and will answer all your
> questions, and save you countless hours of frustration.
> --
> Jerry Boone
> Analytical Technologies, Inc.
> http://www.antech.biz
>
> "Mark" <maworrell@.ananzi.co.za> wrote in message
> news:ddbf09eb.0310231219.20065b09@.posting.google.c om...
> > hope you can help.
> > I need to get my access db backend to sql. I have tried the upsizing
> > wizard but the get message "overflow" and cannot get any further.
> > I also use queries that reference two date ranges from forms such as
> > BETWEEN forms!form1!text1 AND forms!form1!text2. How can i achieve
> > this in an sql view?|||Mark:
> I need to get my access db backend to sql. I have tried the upsizing
> wizard but the get message "overflow" and cannot get any further.
Check this kb:
http://support.microsoft.com/suppor...s/q272/3/84.asp
> I also use queries that reference two date ranges from forms such as
> BETWEEN forms!form1!text1 AND forms!form1!text2. How can i achieve
> this in an sql view?
Might want to look into stored procedures or user defined functions.
You could also apply your criteria after the view is defined. IE:
Select MyInfo from MyView Where MyDateCol Between '2002-12-12' and
'2002-10-12'.
HTH.
BZ
maworrell@.ananzi.co.za (Mark) wrote in message news:<ddbf09eb.0310231219.20065b09@.posting.google.com>...
> hope you can help.
> I need to get my access db backend to sql. I have tried the upsizing
> wizard but the get message "overflow" and cannot get any further.
> I also use queries that reference two date ranges from forms such as
> BETWEEN forms!form1!text1 AND forms!form1!text2. How can i achieve
> this in an sql view?
From Access 2000 to SQL Server 2000
I am in the process of converting from Access to SQL Server.
I am using Access Project to create forms so that I can enter data in tables. I am having problems using the forms, when I use Views or Stored procedures in the forms. Is there any other way to enter data to SQL Server using forms? Thankshave a look at table editor get it here
http://www.2enetworx.com/dev/projects/tableeditor.asp
I don't know if it is what your after, but it could help. You could make a whole web app to input data into the db.
I am using Access Project to create forms so that I can enter data in tables. I am having problems using the forms, when I use Views or Stored procedures in the forms. Is there any other way to enter data to SQL Server using forms? Thankshave a look at table editor get it here
http://www.2enetworx.com/dev/projects/tableeditor.asp
I don't know if it is what your after, but it could help. You could make a whole web app to input data into the db.
Fresh installation and no access
I've just installed MS SQL Server Express Advanced Editon and when loggin in
with my user account(using Widnows Vista) I have no permission at all. I
cant create a new database and I cant change any settings. Then I tried
logging on with the sa account. Then I got this error message:
TITLE: Connect to Server
--
Cannot connect to KULVIS\SQLEXPRESS.
ADDITIONAL INFORMATION:
Login failed for user 'sa'. The user is not associated with a trusted SQL
Server connection. (Microsoft SQL Server, Error: 18452)
For help, click:
http://go.microsoft.com/fwlink?Prod...52&LinkId=20476
BUTTONS:
OK
--
StigStig
During the instalation process, did you set up SQL Server to Windows only
or Mixed Authentication?
I don't have Windows Vista to test the problem, sorry.
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:EE6F52D2-732E-4A27-8285-3B613E1AA262@.microsoft.com...
> I've just installed MS SQL Server Express Advanced Editon and when loggin
> in with my user account(using Widnows Vista) I have no permission at all.
> I cant create a new database and I cant change any settings. Then I tried
> logging on with the sa account. Then I got this error message:
> TITLE: Connect to Server
> --
> Cannot connect to KULVIS\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> Login failed for user 'sa'. The user is not associated with a trusted SQL
> Server connection. (Microsoft SQL Server, Error: 18452)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...52&LinkId=20476
> --
> BUTTONS:
> OK
> --
> Stig|||I thought I set it to Mixed Authentication but now I'm not sure. Is there
any way to change this setting without reinstalling it?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eGrlvS%23MHHA.4928@.TK2MSFTNGP06.phx.gbl...
> Stig
> During the instalation process, did you set up SQL Server to Windows
> only or Mixed Authentication?
> I don't have Windows Vista to test the problem, sorry.
>
>
> "Stig Kulvedrsten" <stig@.spire.as> wrote in message
> news:EE6F52D2-732E-4A27-8285-3B613E1AA262@.microsoft.com...
>|||Sure
SELECT SERVERPROPERTY('IsIntegratedSecurityOnly
') AS
[IsIntegratedSecurityOnly]
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:D25D73BE-1B57-4A7D-9509-52E48E9322C7@.microsoft.com...
>I thought I set it to Mixed Authentication but now I'm not sure. Is there
>any way to change this setting without reinstalling it?
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eGrlvS%23MHHA.4928@.TK2MSFTNGP06.phx.gbl...
>|||ok. i ran the query and got 1 as a result.
but how can I change this setting if I dont have any permission?
Stig
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uo6brH$MHHA.1240@.TK2MSFTNGP03.phx.gbl...
> Sure
> SELECT SERVERPROPERTY('IsIntegratedSecurityOnly
') AS
> [IsIntegratedSecurityOnly]
>
>
>
>
> "Stig Kulvedrsten" <stig@.spire.as> wrote in message
> news:D25D73BE-1B57-4A7D-9509-52E48E9322C7@.microsoft.com...
>|||If you don't , you cannot, unless changing a value in registry ( I don't
recommend you)
You must create a login (to allow connect to SQL Server) then a user to be
mapped to the login to allow access to specific database
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:C945D488-FD52-49EF-9CF0-9D2CC27E64E0@.microsoft.com...
> ok. i ran the query and got 1 as a result.
> but how can I change this setting if I dont have any permission?
> Stig
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:uo6brH$MHHA.1240@.TK2MSFTNGP03.phx.gbl...
>|||You're not getting access because you're not an administrator when you log
in. In previous OS's you had administrator permissions on the database
because you were an administrator in Windows and that made you an
administrator in SQL. In Vista you don't run as an admin by default. You
have to make yourself a Windows admin before you log into SQL so you have
permissions to change the security settings. By the way, this is why they
say you should be running SQL Server SP2 on Vista.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ODSbuP$MHHA.1240@.TK2MSFTNGP03.phx.gbl...
> If you don't , you cannot, unless changing a value in registry ( I don't
> recommend you)
> You must create a login (to allow connect to SQL Server) then a user to be
> mapped to the login to allow access to specific database
>
>
> "Stig Kulvedrsten" <stig@.spire.as> wrote in message
> news:C945D488-FD52-49EF-9CF0-9D2CC27E64E0@.microsoft.com...
>
with my user account(using Widnows Vista) I have no permission at all. I
cant create a new database and I cant change any settings. Then I tried
logging on with the sa account. Then I got this error message:
TITLE: Connect to Server
--
Cannot connect to KULVIS\SQLEXPRESS.
ADDITIONAL INFORMATION:
Login failed for user 'sa'. The user is not associated with a trusted SQL
Server connection. (Microsoft SQL Server, Error: 18452)
For help, click:
http://go.microsoft.com/fwlink?Prod...52&LinkId=20476
BUTTONS:
OK
--
StigStig
During the instalation process, did you set up SQL Server to Windows only
or Mixed Authentication?
I don't have Windows Vista to test the problem, sorry.
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:EE6F52D2-732E-4A27-8285-3B613E1AA262@.microsoft.com...
> I've just installed MS SQL Server Express Advanced Editon and when loggin
> in with my user account(using Widnows Vista) I have no permission at all.
> I cant create a new database and I cant change any settings. Then I tried
> logging on with the sa account. Then I got this error message:
> TITLE: Connect to Server
> --
> Cannot connect to KULVIS\SQLEXPRESS.
> --
> ADDITIONAL INFORMATION:
> Login failed for user 'sa'. The user is not associated with a trusted SQL
> Server connection. (Microsoft SQL Server, Error: 18452)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...52&LinkId=20476
> --
> BUTTONS:
> OK
> --
> Stig|||I thought I set it to Mixed Authentication but now I'm not sure. Is there
any way to change this setting without reinstalling it?
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:eGrlvS%23MHHA.4928@.TK2MSFTNGP06.phx.gbl...
> Stig
> During the instalation process, did you set up SQL Server to Windows
> only or Mixed Authentication?
> I don't have Windows Vista to test the problem, sorry.
>
>
> "Stig Kulvedrsten" <stig@.spire.as> wrote in message
> news:EE6F52D2-732E-4A27-8285-3B613E1AA262@.microsoft.com...
>|||Sure
SELECT SERVERPROPERTY('IsIntegratedSecurityOnly
') AS
[IsIntegratedSecurityOnly]
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:D25D73BE-1B57-4A7D-9509-52E48E9322C7@.microsoft.com...
>I thought I set it to Mixed Authentication but now I'm not sure. Is there
>any way to change this setting without reinstalling it?
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:eGrlvS%23MHHA.4928@.TK2MSFTNGP06.phx.gbl...
>|||ok. i ran the query and got 1 as a result.
but how can I change this setting if I dont have any permission?
Stig
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:uo6brH$MHHA.1240@.TK2MSFTNGP03.phx.gbl...
> Sure
> SELECT SERVERPROPERTY('IsIntegratedSecurityOnly
') AS
> [IsIntegratedSecurityOnly]
>
>
>
>
> "Stig Kulvedrsten" <stig@.spire.as> wrote in message
> news:D25D73BE-1B57-4A7D-9509-52E48E9322C7@.microsoft.com...
>|||If you don't , you cannot, unless changing a value in registry ( I don't
recommend you)
You must create a login (to allow connect to SQL Server) then a user to be
mapped to the login to allow access to specific database
"Stig Kulvedrsten" <stig@.spire.as> wrote in message
news:C945D488-FD52-49EF-9CF0-9D2CC27E64E0@.microsoft.com...
> ok. i ran the query and got 1 as a result.
> but how can I change this setting if I dont have any permission?
> Stig
> "Uri Dimant" <urid@.iscar.co.il> wrote in message
> news:uo6brH$MHHA.1240@.TK2MSFTNGP03.phx.gbl...
>|||You're not getting access because you're not an administrator when you log
in. In previous OS's you had administrator permissions on the database
because you were an administrator in Windows and that made you an
administrator in SQL. In Vista you don't run as an admin by default. You
have to make yourself a Windows admin before you log into SQL so you have
permissions to change the security settings. By the way, this is why they
say you should be running SQL Server SP2 on Vista.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Uri Dimant" <urid@.iscar.co.il> wrote in message
news:ODSbuP$MHHA.1240@.TK2MSFTNGP03.phx.gbl...
> If you don't , you cannot, unless changing a value in registry ( I don't
> recommend you)
> You must create a login (to allow connect to SQL Server) then a user to be
> mapped to the login to allow access to specific database
>
>
> "Stig Kulvedrsten" <stig@.spire.as> wrote in message
> news:C945D488-FD52-49EF-9CF0-9D2CC27E64E0@.microsoft.com...
>
Wednesday, March 7, 2012
freelancing, how to...
My name is Michael, from New Jersey. I have through consulting companies programmed
for over 4 years. I am very strong in most versions of MS Access (VBA too), Excel,
Visual Basic, and Sql Server. My VBA and SQL skills are good, and I have done light
work in Website updates, and the dot net technologies. But consultant companies
exagerate your skills to the client to get as much money per hour while giving you
the programmer as little as possible. I have been inspired to sever the middleman. I
have done light research on how to incorporate, but my question is how does the
marketing process work? Can anyone recommend good websites that teach you how to woe
a major corporation in doing business with you? What are challenges any of you
freelance had to conquer? What forms-online?-are needed to be prepared for an
appointment with AT&T ect human resources/IT dept are needed? Any and all advice are
greatly appreciated from this struggling programmer.
Michael
mikelynn@.comcast.netYou might wanna go through these (http://weblogs.sqlteam.com/markc/)
for over 4 years. I am very strong in most versions of MS Access (VBA too), Excel,
Visual Basic, and Sql Server. My VBA and SQL skills are good, and I have done light
work in Website updates, and the dot net technologies. But consultant companies
exagerate your skills to the client to get as much money per hour while giving you
the programmer as little as possible. I have been inspired to sever the middleman. I
have done light research on how to incorporate, but my question is how does the
marketing process work? Can anyone recommend good websites that teach you how to woe
a major corporation in doing business with you? What are challenges any of you
freelance had to conquer? What forms-online?-are needed to be prepared for an
appointment with AT&T ect human resources/IT dept are needed? Any and all advice are
greatly appreciated from this struggling programmer.
Michael
mikelynn@.comcast.netYou might wanna go through these (http://weblogs.sqlteam.com/markc/)
Friday, February 24, 2012
free distribution of "Database Engine"
Hi:
I'm an asp.net programmer and my database is in access format.
My server is Windows Server 2003 Enterprise Edition Service Pack 1.
I do not need microsoft access installed on my server to access my database through asp.net.
I want migrate my database to sql server 2005
Could I access my database in sql server 2005 format (mdf) through asp.net without sql server 2005 installed on the server?
could I buy to microsoft only "Database Engine"? or
Is there a free distribution of "Database Engine"?
Thanks!!
There is a free version of SQL Server 2005, SQL Server Express..
http://msdn.microsoft.com/vstudio/express/sql/
The data does need to be on some machine somewhere with SQL Server installed.
|||Hi,
You do not need Access installed on the server, only the runtime (which I think ships with Windows these days, at the very worst the runtime is freely distributable if you have VSTO). You should take a look at SQL Server 2005 Express edition (http://msdn.microsoft.com/vstudio/express/sql/download/). Free, and as easy (or easier) to use as Access.
Hope this helps.
Subscribe to:
Posts (Atom)