Recent content by pilsdumps

The best bet is to create a role with all the requisite permissions. The ideal solution is to provide data insert/update/deletes via stored procedures then you can just grant execute permissions on these and not worry about permissions on the tables. If the owner of the table and stored proc is...

When you say its secured, do you mean you've prevented the use of the Shift key on application start up? Usually holding this key on start up will enable the access to tables etc. To secure the sql db you need to manage the permissions of the user. If they're logging in with dbo access then...

Not sure how to fix your specific issue, but a work around is to create an AutoIt script that opens the file then clicks the ok button for you. http://www.autoitscript.com/site/ You can compile the script then get you code to run that.

Yes, SSMS is the main tool for interacting with SQL server. I'm not sure how useful stored procs are for SQL with Access as a front end as I'm assuming you're binding directly to the SQL tables. I steer clear of Access whenever possible and usually use Visual Studio to build .Net front-ends...

SQL server has two security modes, Windows authentication and mixed. If you users are accessing from the same domain, use Windows as users will not need to login manually. To access data, a user needs to have a login and has to be a user of the database. Sql offers fine grain control over...

Use the MVVM design pattern to help keep your concerns separated. If you're not familiar with MVVM and are pursuing WPF I strongly suggest you adopt this pattern as it will make your life a whole lot easier - start here: http://msdn.microsoft.com/en-us/magazine/dd419663.aspx In my design, each...

Its used for checking data concurrency. I don't have a sample to send, but I use it like this: - use a stored proc to get the row data including the timestamp and save this in the front end app (I use WPF) - a user views the data, updates it and saves back to the db with an update stored proc...

You're using an integer not a real number. Just add the .0 to fool it and you're get a more accurate result, then round as necessary declare @birth date = '1980-10-20' select datediff(d,@birth,getdate())/365.0 as age

If you're querying against a SQL Server db you should put the query in a stored procedure and make the required date a parameter of the stored procedure. eg. create proc query_servicedaily_by_date @paramdate date as begin set nocount on select * from servicedaily where date =...

Yep, you can create and edit SQL Server tables etc using Access although there will be issues with compatability depending on the versions of each. For instance, Access 2003 cannot amend SQL Server 2008 tables etc, although you can see the data ok. There are other differences - if I remember...

Hi, My mistake, the solution I gave is for SQL Server rather than Access.

Use regular expressions (namespace required is Microsoft VBScript Regular Expressions 5.5). Reduce the number of potential fields by, for example, looking for fields containing forward slashes or hyphens (based on your examples), then define your regular expressions to match the different...

Just select the records with not exists like this: insert into table1 ( name, date,value ) select a.name,a.date,a.value from table2 a where not exists ( select null from table1 p where a.name = p.name and a.date = p.date and a.value = p.value )

You need to use a subquery to select the 8 records you wish to use and then use this a basis for running your update query by joining to it.

select *, dense_rank() over(order by dag) as _rank from punten_dag