Team929

a few day old question, not all that familiar with php or mysql (is it?) but what the heck. If that ID field is what I think it is (auto counter which is automatically added for you) then you wouldn't need to set that variable when inserting a new value. Just set the variables for the other two columns and the ID should be added for you. Meaning "Insert into username, password values ('newname', 'newpw')" should be enough. Or did I miss you question?

All I can think of is making an mdb and seeing if that works. Again. try recreating the back-end as well if you have not already, although compacting and repairing should help too. If you have a Form on open, then focus on that. If you have a table opening, check the linked table. It could be an MDE issue so try using an MDB to debug. Unfortunately, other that that, I'm out of ideas....

You usually see invalid argument errors when a query, sub, function, etc. is not being properly fed the correct number of inputs. For example, if you have a query to Insert 10 field names into a table that has 9 fields, that would give you an invalid argument. Calling functions and subs in vba without passing the correct number of variables will give the same error. It would help if you could be more specific when (on Form open? on query execute?) and where (vba editor? behind form?) the error occurs along with the exact message again. Hope the above helps.

I remember pounding my head with Access on more than one occasion, I feel you! It's a good program but obviously, it has its drawbacks as well. I don't mind messages but I think it would benefit the greater whole if we kept the discussions here so that others may learn of your fix as well.

Let me see if I understand your problem: -You have the back-end on a network folder. -You have the front-ends on the clients' local drive. -The linked tables from the front-end to the back-end gives you an error. -You mentioned an error in the original post, could you confirm or rewrite what the error exactly says? Some things you can try if you haven't already to hopefully narrow down the root problem: 1. Open and see if you can open the linked tables at all manually inside the table section of the front-end. See if this at least works. 2. Try relinking the tables in the front-end inside one of the user's logins (or a temp user account with the same rights), perhaps the links are off or corrupted. 3. Try recreating a new mdb (i.e. temp.mdb) and link the tables again to see if works. If it works, then there's an issue with the front end. If it doesn't, more likely a connection problem. 4. Browse through Windows explorer to the back-end folder to see if you can even see it. Try opening the back-end file to see if it opens, etc. If it gives you errors, this might give you the hint you need. 5. Try compacting and repairing both files. 6. I have seen cases where linked tables to an Access back-end just does not open, even if you can see the mdb in the network drive. I have had to recreate the folder with the same name in order for it work. If the network folder is located on a client OS (Windows XP) and not on a Server OS (win 2000 server, 2003 server, etc.), it may be the case. 7. Does each client installation of Access fully installed or just the typical installation? Perhaps you made the front-end using a component that is not installed with just a typical installation of Access. Hope this helps.

I'm mainly VB.net, C# to a lesser degree but recently, i see far more .net positions than anything else (C++, C, Java, etc.) but that may be because I'm in my own little world. Breaking down the .net world, it looks like 4:1 in favor of C# over VB. That's the ratio I get after looking through a quite of bit of job postings these past few weeks, even though all the .net languages are pretty much the same thing!

1. Do the users have access to this network drive? MS Access needs rights to create a temp file (*.ldb) in the network folder and without sufficient rights, they will not be able to open them. try creating a text file in the network drive using one of the users' logins to troubleshoot. 2. If you have split up the back-end and front-end, why not just place the front-end on each client instead? Link tables as needed to the backend, however, you will need network access as in #1 above. Having multiple users connect to the same front-end is asking for trouble... Is this even possible? Never tried it... Hope this helps.

I think you may be missing the point of Access... Tables are just to hold the data, not for viewing. Tables should (almost) always be indexed (primary keys). You should always use a query to "view" the data, even if you can just simply open up the table and view it. Also, even if you update the data in a table using a query imbedded in a form, the query should show the correct order of a table with a refresh as long as the tables are indexed properly. With that said, everyone has their own reasons for wanting something a certain way. However, the way you are describing is just not a "best practice" to try to add something in the middle of a table (which is not possible). Insert at the bottom and refresh the form/query/table to view the correct order. Hope this helps.

Not fully sure what you want to do but I guess you have your reasons. However, from a development point of you, is the opening of notepad necessary? I only ask because if you want to take that information inside notepad back to the server side, you're going to have one heck of a time doing that. Anything's possible but I don't know if you want to maintain that. It may be best to just keep everything on the server-side (i.e. just a multiline textbox in the IE screen) and when the client clicks "submit", you can have a very easy time tansporting that information elsewhere. You can store it to a db or export it to the users' machine, etc. >> We are on an intranet and each user has an alias. How do I snag this information? You will need to learn about asp.net membership for this. Hope this helps.

hmm... not quite sure if this is the answer you're looking for but since you're having a very specific issue, how about some workarounds like: 1. putting the batch file lines inside the code itself. 2. Stream read the lines of the batch file (being a text file) through a loop inside your code and running it that way. This way, you also have the flexibility of just modifying the batch file instead. 3. Try older methods of doing this, not necessarily the .net way. I believe there's some examples out there for "ShellWait". Hope the above helps.

http://aspnet.4guysfromrolla.com/articles/052307-1.aspx The link is for a WSAT, probably waaaay overkill for your needs. Perhaps you can strip it down for just for what you need.

Don't know if all OS's have shutdown.exe so you can google and download it as the previous thread says. I believe the one I have used is a stand-alone executable that shuts down the PC and can be called through a script. Or a batch file called from a scheduled task, etc., whichever you like.