Access 2007 front end to SS2K8 problem

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Microsoft Access » Microsoft Access » Access 2007 front end to SS2K8 problem

30 posts, Page 3 of 3

«««1 2 3

Access 2007 front end to SS2K8 problem

Rate Topic

Display Mode

Topic Options

Author

Message

valeryk2000

Posted Friday, August 31, 2012 10:51 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 30, 2013 12:01 PM
Points: 117, Visits: 225

May be just make the form invisible before it can be requeried?

Post #1352974

WendellB

Posted Saturday, September 01, 2012 2:19 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, May 16, 2013 6:46 AM
Points: 106, Visits: 405

The challenge in doing that is to know that the subform controls are displaying "=deleted" - it's not something I've ever attempted. If you can do that then you could hide the subform control until it has been populated. But that text popping up doesn't trigger an event as far as I know, so there's the problem. You could certainly try putting a bit a code behind the "Before Del Confirm", "On Delete", and "After Del Confirm" to display a simple text box message, but I don't think it will work. I presume you have solved the situation where multiple users were sharing the same database and clobbering the temporary table.

Chris makes an excellent point - with SQL Server tables you want to make sure that the have a default value defined for bit fields, or you will have all sorts of trouble. Another thing you should also do is to give each linked table a TimeStamp field. Access is much happier when you do that - if you don't you tend to get ODBC error messages that another user has edited the record, and your changes cannot be saved.

Wendell

Post #1353170

valeryk2000

Posted Saturday, September 01, 2012 2:26 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 30, 2013 12:01 PM
Points: 117, Visits: 225

I'll try. Users now use different files. The only case "=deleted " shows up - when user switches to another case and the subform is reloaded.
Thanks

Post #1353171

WendellB

Posted Saturday, September 01, 2012 2:50 PM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, May 16, 2013 6:46 AM
Points: 106, Visits: 405

That is an easier case then as you know you are getting new data, so you can hide the subform control (set the visible property to No), get the data, and then unhide it by setting the Visible property to Yes.

Afterthought - just out of curiosity can you give us a brief idea of what your application is for?

Wendell

Post #1353172

ProofOfLife

Posted Saturday, September 01, 2012 11:54 PM

SSC Rookie

Group: General Forum Members
Last Login: Thursday, February 21, 2013 9:11 PM
Points: 45, Visits: 9,440

Hi

When you say "=deleted" do you mean "#deleted"?

If you do then I think you have an issue with the primary key on one or more of your tables. One of the common causes of this is the use of the bigint data type for your primary key.

Cheers

Post #1353190

valeryk2000

Posted Sunday, September 02, 2012 6:50 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 30, 2013 12:01 PM
Points: 117, Visits: 225

[b]

Afterthought - just out of curiosity can you give us a brief idea of what your application is for?

Wendell

This is an application with sensitive patient and doctor information. They created an Access database 4 years ago and were constantly updating since then. It has a lot of forms, subforms, reports and subreports. At some moment it occured to the management that the data is not safe in Access. So they told me to transfer the data to SQL Server ... but keep the Access front end intact (I tried to suggest that VB, Java or Web front end would be much better - no way, management was very conservative). SQL statements on the front end would use real table names (as well as linked tables app) with a posibility to read or affect a back end data by a "unauthorized user". So I moved all logics (select, update, delete, etc) to the back end in stored procedures and triggers.
This is a sad story in short
condolences are accepted around the clock 24/7 :-(
Thanks

Post #1353214

WendellB

Posted Monday, September 03, 2012 7:09 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, May 16, 2013 6:46 AM
Points: 106, Visits: 405

I should say! Extended condolences are definitely in order. Crying

There's a common misperception that Access is an insecure system that is also unreliable. As long as you use the .mdb format, you have Access User Security. That feature can be used to manage what various users are permitted to see and do. If you are using an Access back-end for data storage, then there are issues with reliability and with the possibility of theft or loss of the data. But once you put that data into SQL Server on a physically secured server, then an Access front-end provides the fastest development path to a feature rich user interface. With a compiled and properly secured front-end your data is as secure as with any other system.

My prescription for a frazzled and frustrated developer would be a nice long holiday weekend like we are having here, but on a beach or along a quiet mountain brook. (Bad planning on our part to be cutting over a new client this weekend. Crazy

) Hopefully your situation is beginning to settle down and behave as it should, and things will get better.

Wendell
Evergreen, CO
http://www.glmms.com

Post #1353503

valeryk2000

Posted Monday, September 03, 2012 10:50 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 30, 2013 12:01 PM
Points: 117, Visits: 225

With a compiled and properly secured front-end your data is as secure as with any other system.

Compiled - is a key word. Our current wersion is not compiled - simple mdb. That's why all logics is hidden in SQL stored procedures that are called from the front end
==================

Thank you. We have a lot of rain on the East Coast of the country. So ... I enjoy fixing holes in my apps

Post #1353602

valeryk2000

Posted Monday, September 03, 2012 10:52 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, April 30, 2013 12:01 PM
Points: 117, Visits: 225

When you say "=deleted" do you mean "#deleted"?

Certainly "#deleted". Thank you

Post #1353604

sdhanpaul

Posted Wednesday, October 31, 2012 4:17 PM

SSC Rookie

Group: General Forum Members
Last Login: Saturday, May 11, 2013 7:02 AM
Points: 43, Visits: 562

WendellB (9/3/2012)

There's a common misperception that Access is an insecure system that is also unreliable. As long as you use the .mdb format, you have Access User Security.
Wendell
Evergreen, CO
http://www.glmms.com

ah, i have a file..no installation require that I use to get mdb passwords...sorry but its security is crap.

I have a pretty good security procedure working for me right now with them though...anyways...this topic is not abt security...

to the original poster...i noticed your first post is that the user sits and does nothing then suddenly its "=deleted"

i think your connection timed out.

Post #1379557

« Prev Topic | Next Topic »

30 posts, Page 3 of 3

«««1 2 3

Permissions