Recent content by mjmartin

ok, solved the famous #Deleted problem!!! When I say solved I mean completely bodged around the problem :D This lovely thread address most of the issues with MyODBC and Access but I followed everything there and still had the error. But... thanks to a little bit of VBA bodging and trickery...

MyODBC and Access - one step closer Ok this is really bugging me (because I just can't figure it out). I'm using Access with MyODBC (an ODBC driver). Every time I click the new record button, enter some data in and proceed to enter some more data in a sub form in the same form I get...

Ok for searching I want to use the 'filer by form' method in Access. When this user clicks this tool bar, the form goes blank, the user type what they want in the fields they want and when they press the 'Close' button: Access adjusts the filter to records that are LIKE what the user...

Well you could try searching programmers heaven, planetsourcecode and other programming sites for VB6 code. Quite a lot of VB 6 code works in VBA.

It's a matter of opinion but for me the only real difference is in the syntax. PHP's a C / Perl-like syntax but you don't have to bother about memory management (because it's done for you), just like ASP. PHP 5's fully object orientated but I haven't used it yet. Where I stand on the PHP vs ASP...

yeah it worked, sorry I didn't get back to you later. Thanks I'm a PHP guy, last time I used VB was 2 years ago so I'm still a little rusty and that was VB6, Me!ObjectValue looks like a VBA / VB difference, in fact if I recall correctly, the 'Value' property doesn't exist for textboxes in vb6...

RecordOwnerID is a Foreign Key. It's basically logs who created the record.

I tend to use Ghost for all my tests because I don't trust uninstallers. So yes, for testing you'd have to re-install the os everytime unless you use an image program like ghost. I still think Access Extensions rock though because the end user doesn't need to have Access installed. Here's...

Nah you don't need the qualifier, just force of habit on my part. Here's an MSDN doc on making an msi with the runtime and mde For simple packages all you need to do is make an MDE file and use the extensions to create a setup package. Access Extensions give you a royalty free distribution...

yeah I'd just seen that. Doh!!! varX = Access.DLookup("[DBOwnerID]", "DBOwners", "[DBOwnerName] = '" & ownerName.Value & "'") Fixed it. Thanks for the help. My cheesing authentication system is now place :D

It's the value of a textbox. I stepped through the code and that works. I just typed 'mike' in the textbox and even added a msgbox just to make sure it's assigned and it is. The problem's definitely on the dlookup line.

Yeah, it stopped on the dlookup line. That's all the code in the function btw. Database connects btw so I know it's not an ODBC related issue.

The code I'm using for the login click button is: Dim varX As Variant varX = Access.DLookup("[DBOwnerID]", "DBOwners", "[DBOwnerName] = " & ownerName.Value) MsgBox varX Unfortunately when I run that code, Access says: Runtime Error: 2001. You cancelled the previous operation Any thoughts?

dlookup, I'll look into that, thanks. I'm not using the Access security model because I'm only using Access as a FrontEnd to a MySQL database, the Access Front End will then be compiled down using Access Extensions (Visual Studio Tools for Microsoft Office 2003) I'm therefore deliberately...

I have a form called 'Form_show_login' Inside is two textboxes, one called ownerName and one, ownerPassword Also is a button called 'frmlogin' I have two tables, one called DBOwners which has the fields, DBOwnerID (autonumber), DBOwnerName, DBOPass, DBGroupID (f-key) and DBAdmin (bool) And...