Hi All,
From front end application, I execute a SQL
`exec sp_password oldpassword,newpassword
and I got error message :
"Error code# 15002 :[Visigenics] [ODBC MS
SQL Server 6 Driver] [MS SQL Server]
The procedure `sp_password` cannot be
executed from within a transaction.".
If I logged in directly to SQL 6.5 without going
thru the front-end application then I could
change password successfully.
Has anyone tried to change password FROM
a front-end application? Our shop uses
Omnis 7.3.6 as front end and SQL 6.5 as back
end. TIA.
David Nguyen
I'd like to get some help on this. I'm new to SQL Server but am keen to learn it. I have SQL Server 2000 SP4 running and wonder what kind of front end application is best suited for SQL Server 2000.
there is a Crystal Report run from the Front end Application. The DB used here is SQL Server 2008. I need to know the Stored Procedure used by the report that is been run from the front end. . How shall I do it?
in create a new software application using C# as front end and database with sql. how to connect SQL server with my front end application.dot net training in chennai <a href="http://www.fita.in/dot-net-training-in-chennai/">Dot Net Training in Chennai</a>
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)?
Hi there,I sincerely hope that someone out there can help. I have twoinstances of the SQL 2000 Desktop Engine running. One is on my localmachine for development and the other is on another machine on ournetwork which is the production environment. I have built an Access2003 front end application which connects to this database. Thisworks fine locally, as you would expect. I successfully installed thedatabase on the production machine and am able to connect to it viaAccess 2003 (using the Data Link Properties window) and from thirdparty database manager software (similar to Enterprise Manager). I amnot able to to connect to the database via my application.I am using the "sa" account with a strong password. This is myconnection string:strConnection = "Provider=sqloledb;DataSource=server02;UserId=sa;Password=strong;Initial Catalog=Test"The error I'm getting is:"Connection cannot be used to perform this operation. It is eitherclosed or invalid in this context."The connection string is the only thing that changes in my code when Iswitch from my local to my production database. Is there some reasonthat I can't use the "sa" account in this fashion that I'm not awareof? I'd rather not use integrated security for simplicity's sake asthis is a small, internal application. Also, I would have thoughtthat if that was the issue, I couldn't use "sa" at all, even locally.I'm going to post to the Access group as well but thought someone heremight have some advice to offer as well.Thanks,Barb
4 Layered Web Application for Inserting data into a database using sql server as the back end and a web form as the front end using C# . Can someone provide with code as I am new to this architecture and framework. Better send email. Thanks In Advance, A New Bie
I'm using Access 2000 and have tried Access 2003 front-end to executethe stored procedure sp_password on SQL Server 2000. I continue toreceive the following message: "The old (current) password was notcorrect. Password not changed." If I go into query analyzer and runan execute @old, @new, @loginame with the same values as passed to mycommand collection in Access, it works just fine. I'm using WindowsAuthentication and my server is defined for SQL Server and Windowsauthentication. I have tried using the sqladmin account and havereceived the same error message. I have verified the old password andI know it is correct because I am able to change the password byexecuting the same stored procedure in query analyzer. Why are theresults different? How can I resolve this problem?
Greetings all. I am currently working to improve the security on a legacy application we have at my company. The app was written in vb6 years ago. We now have the app running against a sql 2005 server. One of the function/screens in the application is used to administrate users. (each user has a sql user id) and one of the functions is to reset the password. The vb code uses a call to sp_password. Here is the problem. We setup a network sniffer and found the command being in plain text. While the user logon is encrypted ( SSL Fallback) the sp_password commands issued by the app are plan text. Anyone know of a way to make this encrypted? Leif
Executing sp_password with an incorrect old password gives the error: "Msg 15151 Cannot alter the login 'TestUser', because it does not exist or you do not have permission."
This is very unhelpful, considering the user does exist and I do have Alter Any Login permission. If I supply the correct old password, sp_password executes correctly.
Is this by design? Is it a security concern to inform the user that they're specifying an incorrect old password, thus allowing them to try another one (repeatedly)? Is there any way that I can check to see if the old password is valid? Or do I just have to first check if the login exists, then check if the current user has permissions, and then know that if sp_password fails it's because the old password is invalid?
have SQL Server 2005 std edition SP1 installed on Windows 2003 Std edition .Configured Transactional (single Publisher and no clustered environment.) Replication past two months working fine, Now 1.Distrib.exe application err is coming.
Due to which my job is failing (Distributor to Subscriber). Iam attaching thw file. Thanks Sandeep
Sorry for the lengthy question, but here goes: I currently have an access database with a FE and BE that resides on each users laptop. Weekly they connect to the network and synch the BE the master on a network drive. There are numerous propblems with this as it has grown quite extensive.
We would like to have this be a server based database with the remote users either having access through the web or something else?
A few of the capabilities of the current database: 1. generate and print reports 2. update project forms. 3. enter time logs 4. enter notes
My question is: What are my options for a remote FE? I am well versed in VB6 and Access. Would be willing to learn other languages (VB.net, my SQL, etc.) Would I be able to have the same functionality or would I have to have separate software for certain functions?
Hi, If I don't have any visual studio design tools etc. Is there any way I can build a simple form that will allow users to view, insert, update and delete single rows from a SQL 2005 database? Or is there any free downloads that might help. the table is really simple and has only 4 fields
I am new to SQL Server. I currently have an Access 2007 database and next year my client would like to migrate to SQL Server. Which Front End is the best...Access, VB.net or some other platform altogether?
I'm doing a database for employee info and thier payroll.. im using SQL Serevr 2000 and IIS but i'm not too sure what to use as the frontend, a VB would kinda be overkill because each employee just needs to be able to update his own info and addresses, maybe a XML or some other page that uses windows logins for authentication? any ideas, this is my first project like this on on a college Coop
i am almost finished building the front end for an application to manage restaurants. i am developing the front end with access vba, and intend to use sql server as a back end for the service. i just came across a group of people bashing access developers on a different site. i have several restaurants interested in using the service, and believe that the service should be very successfull (i have a very specific customer base that is currently not being targeted). the access component would not be a multiuser application. before i distribute the app i would appreciate any input. am i getting myself into trouble using access vba? should i run scared and switch to a vb.net web service? thanks in advance for any thoughts.
Below is a post by blindman from my other "mentoring" thread (http://www.dbforums.com/showthread.php?t=1608569). I wanted to respond to it but not in that thread:
Yeah, but if he's going to go unbound he might as well develop in .Net rather than Access. You lose half the convenience of MSAccess as a front end if you use unbound forms and controls.
Besides, he's trying to learn SQL Server, not front-end development. Learning both at the same time may be a bit much. I'd suggest he stick with his idea of converting the Access database to SQL Server back-end.
But, you should definitely convert the Access front-end to a Microsoft Access Data Project, rather than a classic mdb file.
Going unbound would increase your application performance, but probably not noticably unless you have scores of uses, and since you are currently using straight MS Access I'd guess you have no more than five or six simultaneous users, right?
blindman
To start I have decided that ADO is the way to go even though I don't necessarily need the performance boost for my current situation. Keep in mind I am planning for future and more demanding opportunities, hopefully :) And I'd like to learn the "right" way to do things.
I actually use ADO quite a bit in my current DB app and bound controls as well so it really wasn't a new concept. However using strictly ADO produces alot more work and code. And like blindman says it pretty much takes all the ease of Access away and VB.NET for that matter too. I mean all the wizards are useless. So I have two questions:
1. When going to all ADO you are pretty much recreating what Access already does for you right? Coding in ADO is more work right? I mean you have to setup connections and fill fields and listboxes manually in code right? I don't mind the extra work I just want to make sure if I'm going to be doing all this extra coding that it is the right thing to be doing.
2. MDB vs. ADP - From what little I've read Access Data Projects are made for use with SQL Server. It is even more useful if you don't/can't actually work in SQL Server. But again if I'm using ADO it strips all the usefulness of the ADP's doesn't? I don't need ADP's to create views or sprocs. I can do all of that through the management studio. So does it really matter if I use an ADP or MDB as my front end if that is all it is going to be is a front end?
Lastly I wanted to use VB 2005 as the front end but we utilize a ton of reports. As far as I know Crystal Reports or something like it has to be used with VB 2005. Or does VB 2005 have some built in reporting capabilities? I thought I saw some report designer for VB6. Anyway I decided to stick with Access because I am familiar with its reporting capabilities.
I should note that I have VB 2005 Express and SQL Server Express. Right now my company is not putting any money into a higher version.
Is there any front IDE for MS SQL as there is MySQL Front for MySQL. Iam looking for it so that it is easy to quickly add/edit/delete thedata from the existing table. Please prode the Download URL is there isany.Regards.
Hi!I'm trying to build an app. for my parents' office. They have a smalloffice (5 PCs), and they currently work with a very old program that'sbased on DOS. The program doesn't work well under XP, so they still useWin 98. They had their network upgraded about a year ago. They hadMicrosoft SBS 2000 installed, it includes SQL Server. I've written afew DB's in Access before, and now I'm just learning how to use SQL.Before I start work on their app., I have a question:I know it's possible to create an interface that can be put on theirnetwork and accessed via a browser. How is this done exactly?It would be very beneficial for me, because it would mean that the newapp. would be platform independent, so that they can upgrade to XPeasily. It would also save us the cost of licensing front-end software(e.g. Access) for each machine.Any comments would be appreciated.Noam Nelke, Israel.
Hi all,I have a number like so 778625 and want to make this a more meaningfuldate (UK) so how difficult is it to add two digits in this case 19 tothe front of this number?Many thanksSam*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
I have created a Database Editor with FrontPage using the Wizzard. I have adatabase in SQL 2000 called Equipment with one table named Equipment.When I bring up the editor, it displays a list of all records with a link tothe edit page. When I click on the link for the first record on the page,The edit page come up correctly. I can edit the page and then submit it.When I click on the link for the second record ( and all the rest of therecords) in the list I get the following message:Database Results ErrorDescription: [Microsoft][ODBC SQL Server Driver][SQL Server]Syntax errorconverting the nvarchar value 'BF176' to a column of data type int.Number: -2147217913 (0x80040E07)Source: Microsoft OLE DB Provider for ODBC DriversWhen I click on the link for record BF176, which is about 20 records downthe page, I get the following message:Database Results ErrorDescription: [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid columnname 'BF176'.Number: -2147217900 (0x80040E14)Source: Microsoft OLE DB Provider for ODBC DriversI have gone in the SQL database and messed arounf with changing the columntype from nvchar to nchar and changing the length, but can not figure thisout. I cannot tell whether this is a Frontpage problem or a SQL problem.Any help would be appreciated! Thanks!DarrenMCP
I have a scenario while creating a report where I need to maintain the same number of rows for a column, even if the data grows or shrinks for that column
example
Each Scenario is grouped by ID
Scenario 1
columnA
Row1 X X Row2 X Row3 X Row4 XYZ
Scenario 2
columnA
Row1 XA Row2 XYZ
In both scenario's I need to control from front end
Hello all. Yes, this is another question relating to how to make a front-end to a SQL database using ASP.NET. I performed a search in this forum and did not find the exact answer to my questions (one responder to the other threads about this topic even said this is the incorrect sub-forum for this question, but I found no other appropriate place; considering this sub-forum is for asking beginner questions).
Besides the "quickstart" tutorials linked off this site, can you point me to other web resources (tutorials, walk-throughs, etc) or books that would provide the necessary information to develop a SQL front-end? Specifically I need help creating the Update Record and Delete Record pages.
I was hoping a "rapid development" tool could be used. At my disposal I have Visual Studio .NET 2003, Dreamweaver MX 2004, and FrontPage 2003.
I am using Access 97 as a front end to access SQL 7 server on NT 4.0 server. I've set up security model based on NT authentication only. Users have login right to login to SQL and they have public & dataread & denydatawrite access. They also have SELECT permission on a table object and have no permission to INSERT, DELETE and UPDATE. When I use Access 97 to access a database, users are still capable of inserting and deleteing records in tables.
Maybe because I have worked mainly with VB as a front end to SQL Server so I am biased, but I now need definite reasons (I am on a committee for potential future directions) for using VB as opposed to Access for front ending SQL/Oracle, etc. I would also like to use ADO as oppose to DAO. Right now we are using Access with DAO.
We have just moved a largish Access database (180mb, 78 tables, largest tables have about 250k records) to SQL 2k. The original app had an Access back end (now loaded to SQL), and an Access front end (on each client) which is using some local temporary tables, about 600 queries, and several thousand lines of code using ADO and DAO). The Front end was relinked to SQL back end. When testing everything seemed to run OK, but under load (15-20 users) the new app just crawls. Routines that used to take seconds now take 10s of minutes. ODBC timeouts or blocks are common.
Any idea why should the SQL back end be so much slower than Access. both the Access back end and SQL2k are on the same server (Win 2k Adv. with RAID 5, dual 600mhz Pent III, 512Mb RAM). I realize that Access is not the best front end but that is what we have to work with.
Any help would be appreciated, as I am ready to swith back to Access.
My company uses MS SQL Server for the back end and a Retail specific CRM as the front end. I wish to develop some internal peices of software for our use. I was planning on doing this with access.
my options are:
*Use access as front end and backend *Use access as front end and SQL server as backend (create new DB) *Use other front end and SQL Server as backend.
My question is, what are some good front ends that are availble for reletively small demands? How does Visual Studio come into play?
*Also, I would prefer to be able to create a .exe. I dont think access alows that. I would not want users to be able to go in (or even see) the tables and queries. They should only be able to see the one main menu form at the very least.
When I build an MS Access front-end for an SQL Server backend, how does it take care of data integrity and concurrency , if it is only a front-end ? Is Access smart enough to do the job ?
Does anyone have a favorite tool/system for creating a SQLServer front end?
I've been looking into this myself and seeing everything from Visual Basic to Access to ASP, from Web to Windows.
Here's my situation. I need to create a few simple tools for our office folks to use. For example, a tool that creates an invoice using data from two tables (Customers, Items).
I'd like to make it as simple as possible for them (ex. setting up an autocomplete for the customer name, etc.).
Please understand, I'm not looking for anyone to write code for me. I just want some feedback on what tools to use.
I would just use Access (since I am familiar with it), but we don't have it here. Sigh.
