Search results

Firstly, the coloring. Secondly, it seems there is more whitespace, making for an easier scan/read.

Ah, here is the thread https://www.access-programmers.co.uk/forums/threads/my-current-version-of-front-end-updater.305926/#post-1631178 It turns out, the delete command wasn't working back then either, lol. Well, it must have gotten pushed to the very back burner. It's on the front burner...

Forgive the late post on an older thread: I have been using this code from Scott for a while, and am working on a new project, using the same code, but slightly modified. Only now, the batch file does not delete the local FE file. I believe I have a thread with this code posted...

Jon - Logging back on to this site and seeing the new look and feel...it's pretty awesome. I thought I had the wrong web address at first! I haven't checked things out yet, but so far I love it!

Colin, I appreciate the work you've done on this, and I have a quick question: Why is it necessary to run the SQL UPDATE for the Remote user code? Ok, two quick questions: Why is the SQL updating CurrentDB = True, when in fact the BE i am connecting to is on a server, and it is not on my...

My answer was "Yes", and here's the provider info: Provider=Microsoft.ACE.OLEDB.12.0 So, a linked table worked for you...I feel stupid. I am using a test DB that I did not refresh the links in... Anyway, a follow up question regarding connection properties: How would you specify each property...

Yes. Well, I just discovered that this will not work with a linked table, which "Users" is. It does work with a local table. How would I change this to support a linked table? Would I need to change the connection string to connect the source DB?

Apparently this code is supposed to populate a recordset based on the "Users" table. It's just an example from the book on using the Command object. The goal is to ultimately find out what is causing my DB to get corrupted/become unrecognizable, so I am looking at moving some forms to unbound...

I usually have several copies of the front end and back end. For production, the front and back ends are stored on the server, and I use a batch file to backup those files to another location. This way I can use the task scheduler to call the batch file. The development front end is usually a...

So I am playing around with ADO connections, and got this bit of code from a book: Microsoft Access 2013 Bible Public Function ExecuteCommand() Dim adRs As ADODB.Recordset Dim adCmd As ADODB.Command Const sTABLE As String = "Users" Set adRs = New ADODB.Recordset...

That could very well be.

What is your front end going to be to connect to SQL Server? I have been using Excel for import/export, and that can be done via linked tables and VBA. The main issues I have had to deal with is the data itself - spelling errors, spelling variations (which means duplicate records in some...

A good chunk of this code came from Scott L Prince, which is based on code he got from Bob Larson via StackOverflow.com. It has been adapted to fit into any DB I have created so far. The current table setup goes like this: • An admin back end that handles the versioning info, file names...

And file back up made!

Ahhhh, yes, the import worked. So, lesson learned, and thanks again for the quick responses.

Well, looks like this a do-over! Fortunately it's not a critical db and I get paid by the hour, lol. Thanks guys! Backup copies are a very good thing to have! :)

How can I do that if I cannot open the FE? Unfortunately, I did not back this up before splitting...never had this issue before and was going to back up after the split. I just realized that I took a previous FE, developed on that, dumped the old tables, and split again. Not sure if this...

Hello all, I just split a DB that I had put plenty of time into, and now I cannot open the front end. It is recognized as an accdb file, when I double click or press enter, Access opens to the 'Choose Your File' screen. It shows the file size as 7.25MB, has no password, not hidden or...

Well, I discovered something that did help: Const conJetDate = "\#mm\/dd\/yyyy\#" sfilter = "[DueDate] <= " & Format(Date - Weekday(Date) + 7, conJetDate) & "" By using a date format, which I had gotten from Allen Browne's website some time ago, and used in another database, Access deemed it...

Private Sub cmdCurrentWeek_Click() ' filter for this week's PMs Dim dDate As Date Dim lToday As Long Dim sfilter As String Dim dToday As Date dDate = Date - Weekday(Date) + 7 ' lToday = CLng(Date) ' dDate = CDate(lToday - CLng(Weekday(CDate(lToday)) + 7))...