Recent content by ucinv

Maybe I'm confused by what you're asking but, have you tried right-clicking on the tab page you want to paste into and select paste from the menu that pops up? Depending on the amount of controls, the pasted items may show up at the bottom of the page... If you do not have the entire tab page...

I had a similiar problem in my Access 2000 w/SQL SERVER 7 app. Maybe this function will help you do something similar: Public Function HandleApostro(astring) If Not IsNull(astring) Then If InStr(1, astring, "'") > 0 Then HandleApostro =...

I see that sysusers table contains user logins and roles. Is it safe to add a new column in this and other system tables? I wouldn't be manually creating user or changing keys, indexes, etc.

I found that my service startup account in the SQL server agent properties was not set properly. It was set for localsystem but was fixed by changing it to mydomain\mysqlserver. Now everything works normally.

I'm having problems with running jobs on SQL Server 7. They seem to run and finish just fine, but the status always says 'Executing Job Step 1 (Step 1)'. I can't seem to find any problems in the server's event viewer log nor the errlog or the sqlagent.out files. I think maybe SQLagentCMDexec...

I have found that SQL stores the user info in the Master database in the sysxlogins table. I should be able to make this work. Thanks for your help.

Thanks for your help LittleSmudge, it sounds like a better idea, and easier to implement (less code). I'm new to SQL Server 7 and am unsure about the Users table you refer to. Is there a Users table in SQL? I have not manually created one myself because I want to manage users at one place only...

What I want to do is make a switchboard that will display certain items on a per user basis, without hardcoding the users names. Info: I am running SQL Server 7 with Access 2000, using ADO for programming. This need started because we had 2 databases in Access 97. Eventually they got migrated...

From what I know about ADO, there is no longer .findfirst. Additionally, you can't specify multiple fields in the .find statement. Also there is no longer a .nomatch. Your code would end up looking like this: Private Sub CboCompany_AfterUpdate() Dim rs As adodb.Recordset Set rs =...

Although this post is old, maybe this info might help others: By default, .ADP's use ADO. Either change your code to use ADO or set your references to use DAO.

Is there a good working ldb viewer for Access 2000? The one from MIcrosoft worked great with Access 97, but with Access 2000 shows strange results. For example when a user logs off Access, it shows them as being suspect although the database is fine. I've tried several other options and more...