To clarify, you're using an Access front-end with connects to SQL backend?
What is the code behind your data entry form? (specifically the connection and command objects)
~Melagan
______
"It's never too late to become what you might have been.
Hmm...I was just browsing around and found this older thread: thread701-941309
The Switch() function looks promising.
~Melagan
______
"It's never too late to become what you might have been.
Is Revision_Version being stored as a string? Is it a number? If it is a number then use the appropriate definition - Long (or Integer depending on the length of your number). That aside, just a personal preference on error handling - I like to include the error number.
Private Sub...
I've run into issues with Outlook 2003 + ACT 2007 integration and have been able to resolve most if not all by deleteing / reconfiguring the ACT Address Book. Make sure the username and password are correct when you set this up.
Also, double check that microsoft word is not set as your email...
Oops - my line should go after: If .Show = True Then
Incidently - if you wanted to allow multiple selections, something like this would do the trick.
[code]
Option Compare Database
Option Explicit
Private Sub cmdOpen_Click()
'Requires reference to Microsoft Office 10.0 Object Library.
Dim...
You are 99% there man - all you need to do is add this line before End With
MsgBox .SelectedItems.Item(1)
~Melagan
______
"It's never too late to become what you might have been.
This is just a guess - not sure if it'll work; I'm assuming you're using this on a form or report.
If [Format] = "Currency" Then
Me!myField.Format = "Currency"
Elseif [Format] = "Percentage" Then
Me!myField.Format = "Percent"
End If
..just a shot in the dark. I can't even test it right...
Yes that is clear. Queries do not have field definitions like tables do, though. What method are you using to send your query to Excel? Are you doing it programatically or manually?
~Melagan
______
"It's never too late to become what you might have been.
My pleasure - I'm glad it worked out! I would like to ask anyone else who has been watching this thread if they would have had a different approch to this project. This was the first thing I thought of but still wonder if there are any other (simpler) ways.
Cheers~
~Melagan
______
"It's never...
I'm not quite sure I understand the question - or maybe the reason for the question. What are you wanting to do with PM Basis? Is this a text box on a form or a field on a report?
~Melagan
______
"It's never too late to become what you might have been.
You probably have your Immediate window hidden. In your code window, hit control-g to show it. If you don't have any luck with that - change this line:
Debug.Print strSQL
to ...
Msgbox strSQL
The goal here is to see the SQL in a more readable format and make sure that it is pulling the value...
My bad - I meant to concatenate all of those fields into one field. Try this for strSQL.
strSQL = "SELECT TBL_CARRIERS.PREFIX & " _
& "TBL_RECIPIENTS.PHONE & " _
& "TBL_CARRIERS.SUFFIX & " _
& "TBL_CARRIERS.DOMAIN AS theRecipient" _
& "FROM...
Alrighty - I understand where you're at now; no problem!
The thing with SQL is that you can not, to my knowledge, directly populate a variable using SQL alone. If you are really wanting to use SendObject, then you're going to have to put your SQL into a recordset and then populate your variable...
Where does this 'FOO' variable come from? Are you using the above SQL to populate a recordset, then populating your FOO variable from said recordset?
There are some guys here that are smart enough to put a solution together with all of the given information, but I am not one of them :) I need...
One thing I've noticed about Access User Level Security is that the login dialogue box automatically fills the username field with your windows profile username. If you create each user with the same username in Access as Windows, that'll save your users from having to type in a (different)...
Why not just build Access user accounts under Tools > Security > User and Group Accounts ?
To take full advantage of Access User Level Security, each user logging into the database should have their own username and password.
If the database is on a network with multiple LAN users logging in...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.